2 * client library uses as much krb5 as possible to talk to krb4
3 server, converting tickets and whatnot. This will be mostly
4 ripped out, but serves as a proof of concept. Client will
5 successfully receive new-style checksums, but this code won't be
9 * server will accept new-style checksums and authenticators, as
10 well as old-style. It will never send them, and "bad things"
11 will happen if non-DES enctypes get used.
12 * Note that this will allow krb5 interrealm clients, and there
13 are no brain-dump issues to deal with. This is aesthetically
17 * client sends only new-style messages
19 Milestone 3.5 (in progress) [done?]
20 * refactor checksumming code
23 * Desired end state that server uses the old checksum for single-des keys,
24 and new checksum for everything else, thus the first clause in the
25 following is obsolete:
26 This may be the case, someone needs to check.
27 * server sends only newstyle messages, and can't brain dump the
28 new keys. (this tests the codepath opened in milestone 1)
31 * server can send new or old-style messages depending on how the
33 * server can brain dump newstyle keys, and figure out whether
34 the rest of the federation speaks them.
37 * zhm can figure out what sort of realm it's talking to, and
38 communicate this to the client.
41 * Send this to Derrick.
44 * brain dump via krb5, encrypted
45 (optional) brain dump to/from file
48 * bring sourceforge up to date
51 * cough up a release of sourceforge