Skip Menu |
 

From: jaltman@mit.edu
Subject: SVN Commit
The WinLogon event handler in prior versions of the Wix installer
has been installing the event handler under the registry value "KFWLogon"
which happens to be the name that "OpenAFS" also uses for its Kerberos
logon events. The KFW NSIS installer has used "MIT_KFW" in order to
avoid the conflict. The Wix installer is being corrected to match.

When there is a name collision, only one of the event handlers gets
installed. As a result, Kerberos FILE ccaches get created with SYSTEM
only ACLs and are never destroyed. This is the same problem that
happens on Windows Vista when integrated logon is used because the
event handler hooks do not exist.


Commit By: jaltman



Revision: 19290
Changed Files:
U trunk/src/windows/installer/wix/files.wxi
From: tlyu@mit.edu
Subject: SVN Commit
pull up r19290 from trunk

r19290@cathode-dark-space: jaltman | 2007-03-27 09:46:13 -0400
ticket: new
subject: WIX installer stores WinLogon event handler under wrong registry value
tags: pullup
component: windows

The WinLogon event handler in prior versions of the Wix installer
has been installing the event handler under the registry value "KFWLogon"
which happens to be the name that "OpenAFS" also uses for its Kerberos
logon events. The KFW NSIS installer has used "MIT_KFW" in order to
avoid the conflict. The Wix installer is being corrected to match.

When there is a name collision, only one of the event handlers gets
installed. As a result, Kerberos FILE ccaches get created with SYSTEM
only ACLs and are never destroyed. This is the same problem that
happens on Windows Vista when integrated logon is used because the
event handler hooks do not exist.




Commit By: tlyu



Revision: 19339
Changed Files:
_U branches/krb5-1-6/
U branches/krb5-1-6/src/windows/installer/wix/files.wxi