Derrick Brashear wrote: > i disagree about distribution. i do think we should have a page with > instructions and resources we provide a reference to. > > On 10/25/07, *Jeff Blaine* < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > IMO, it should be distributed with it and referenced > in a new README.kaserver (which also should include > the elders EOL statement regarding kaserver). > > It doesn't have to be referenced by the build process. > > I wouldn't surprise me to find that nobody agrees with > me again.
I agree that it is stupid at this point for administrators to be forced to track down the remnants of Ken Hornstein's afs2krb5 migration kit in order to obtain the one missing piece that is neither distributed with OpenAFS or MIT Kerberos. Given that the afs2k5db tool is a Kerberos tool that requires explicit access to internal Kerberos data structures. I would argue that it really should be distributed as part of MIT Kerberos much as fakeka is distributed as part of MIT Kerberos. The point of the tool is to help you migrate your KDC to MIT's KDC. Making it easier to do so should be a job of each Kerberos distribution. Since MIT won't ship it, we should provide a pointer to the remaining sources. It would be nice if someone would extract the necessary pieces from the afs-krb5 kit and repackage it. Perhaps even port it to more recent versions of MIT Kerberos. Then OpenAFS can provide a pointer to it. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
