John Tang Boyland wrote: > I have been strongly recommending my students install OpenAFS > on their home computers, but none has been able to get OpenAFS > to work on Windows Vista. Apparently the latest version of > Kerberos For Windows 3.2.1 doesn't include the AFS functionality, > (the AFS tabs don't appear etc) > but 3.2.0 "locks up" if it is used instead. I apologize for the > imprecise bug reporting (I don't have a Windows machine myself), > but I was wondering whether anyone has been able to get OpenAFS > 1.5.21 to work on Windows Vista with MIT KfW. Perhaps there > are some installation instructions that we missed? > Is there some required order of installation? Does an AFS plugin > have to be explicitly installed? How is that done? > > Regards, > John Boyland
In my opinion, MIT KFW 3.2.1 should not be used. My recommended version is 3.2.0. MIT's windows developer made several changes to Network Identity Manager in KFW 3.2.1 that make it in my opinion significantly worse. Corrections have been submitted to the repository and will be included in KFW 3.3. In the meantime, KFW 3.2.0 should be used. When KFW 3.2.x is installed without OpenAFS for Windows there will be no AFS support in Network Identity Manager. KFW only ships with Krb5 and Krb4 credential providers. The AFS credential provider for NIM is shipped as part of OpenAFS 1.5.x. The currently recommended release of OAFW is 1.5.21. It does not matter which order the two products are installed in. Follow the directions in the OAFW Release Notes for configuring NIM to obtain credentials for your AFS cells once both installations have completed. If you are using 64-bit Vista, you must install three packages: * OpenAFS for Windows 64-bit * OpenAFS for Windows 32-bit Tools * MIT Kerberos for Windows MIT KFW is a 32-bit application and if you do not install the OAFW 32-bit tools you will not have a NIM AFS credential provider or a working aklog. Jeffrey Altman Secure Endpoints Inc.
smime.p7s
Description: S/MIME Cryptographic Signature
