Now that is a blast from the past. Aleph was built on top of Columbia University's Kermit95 which was one of my prior software projects.
For those who attended the AFS and Kerberos Workshop last week, it is exactly because of this type of version conflict that the forthcoming Heimdal release for Windows from Secure Endpoints will be installed as a shared side-by-side assembly instead of as a loose collections of DLLs located somewhere within the PATH. Jeffrey Altman On 6/3/2010 3:42 AM, Michael Richter wrote: > It's working now! > The problem was caused by another Software (Aleph) which installed it's > own very old Kerberos in \Windows\system32. I deleted these files and > now it's working. Now Aleph uses the new Kerberos files too. > Thanks for your help. > > Michael > > schrieb Jeffrey Altman: >> On 6/1/2010 8:21 AM, Michael Richter wrote: >>> I tried to set KFW and AFS paths on first position in PATH but it didn't >>> worked. >>> >>> And I tried logging before but the eventviewer said only: >>> ~~~ >>> [AFS Client] OpenAFS Start Pending. >>> [AFS Client] Security Level is Clear. >>> [AFS Client] OpenAFS Running. >>> [AFS Logon] Integrated login failed: Authentication Server was >>> unavailable >>> ~~~ >> >> If these are the only messages being logged, you have not turned on >> integrated logon debugging. >> >>> I tried now KFW 3.2.3 alpha but it made no difference. >>> >>> Would it be an option to copy all KFW files to \Windows directory? >> >> Absolutely do not do this. >> >> >
smime.p7s
Description: S/MIME Cryptographic Signature
