Neulinger, Nathan wrote:
Of course, the main question is how you want to handle the external krb5 dependency. I haven't looked at the windows build to see how that one is being done.
The OpenAFS Windows tree contains a copy of the MIT KFW SDK. aklog.exe
is linked to the KFW libs in the SDK. Since aklog.exe is useless without the presence of the Kerberos libraries I have not bothered to
conditionalize the run-time loading.
My guess is that on Unix the hard part will be determining whether or not a version of Kerberos is available; and depending on the version Heimdal or MIT 1.2 or MIT 1.3 do the correct thing to build the executable.
Stripping out the Windows code is certainly one direction that could be taken. However, from a code support model I would prefer if the two forked implementations were merged.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
