3
* unix_time.c also exists in ../krb4, and they're different; both
4
should probably call into the krb5 support anyways to avoid
9
* Check include/kerberosIV/des.h and see if all the prototyped
10
functions really are necessary to retain; if not, delete some of
13
* Much of this code requires that DES_INT32 be *exactly* 32 bits, and
16
* Array types are used in function call signatures, which is unclean.
17
It makes trying to add "const" qualifications in the right places
18
really, um, interesting. But we're probably stuck with them.
20
* quad_cksum is totally broken. I have no idea whether the author
21
actually believed it implemented the documented algorithm, but I'm
22
certain it doesn't. The only question is, is it still reasonably
23
secure, when the plaintext and checksum are visible to an attacker
24
as in the mk_safe message?
26
* des_read_password and des_read_pw_string are not thread-safe. Also,
27
they should be calling into the k5crypto library instead of
28
duplicating functionality.