Lars Richter wrote: > Hi, > > I have a strange behavior with the new release of openafs. > > I tested openafs-1.4.2.-beta1, because of problems with some office > tools. Now I want to update all the computers in our production > environment from Version 1.4.1 on 1.4.2. After the installation I get no > token during login. After login I could obtain a token manually. When I > step back to 1.4.1 or 1.4.2-beta1, there are no problems. > > I set the option to debug the integrated login. Sometimes I don't see > messages about AFS-Logon and sometimes the message appears > "Authentication server was unavailable". > > Are there any changes? Or does anyone have an suggestions? > > Regards, > Lars
There have been many fixes to afslogon.c since Beta 1: * no longer obtain kerberos tickets if the OpenAFS Service is disabled * no longer all PTS auto-registration from Integrated Logon * do a better job of restricting Kerberos tickets to the user session they belong to * store Kerberos tickets in the user profile temp directory instead of a system temp directory * prevent a Windows blue screen We would need to see the log messages and we would need to know if you are using KFW or not and what version it is before any useful assistance could be provided. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
