[pubcookie-dev] Windows 2k3 3.3.0a registry problems
dors at cac.washington.edu
Wed May 10 09:22:44 PDT 2006
Yep, we've seen this here. I first saw it myself while testing the
fixes made for appID inheritance and noted it in the install guide
under Known Problems:
"MMC adds empty registry keys. The MMC extension adds empty,
harmless, but nevertheless extraneous registry keys when you open
the Pubcookie Directives tab."
It wasn't seen as a showstopper for the 3.3.0 release, so it was
prioritized to be looked at later. I agree, it's probably a logic
On Tue, 9 May 2006, PHILIP D JOCHIMSEN wrote:
> Well, I have managed to find another interesting dilemma: extra
> keys & entries, like below.
> Actual directory structure:
> Structure recorded in the registry:
> /root/protected/error/protected **no actual config info**
> /root/protected/error/protected/error **no actual config info**
> /root/protected/protected **no actual config info**
> /root/protected/protected/protected **no actual config info**
> /root/protected/logout/logout **no actual config info**
> It certainly appears to be a corruption of logic when changing the
> of a directory that has already inheritied an App ID. The use for this
> is to designate different appID's for different parts of a completely
> pubcookie protected site.
> I can duplicate the worst symptoms of this problem by changing
> on the inheritied directory, hitting apply and then hitting ok. The
> extraneous registry entries do not appear until after ok has been hit.
> If I never hit apply, it works correctly. So...what does "apply" do
> "ok" doesn't realize has already been done?
> Has anyone else seen this before?
> Phil Jochimsen
> Web Technologist
> UW Madison
> pubcookie-dev mailing list
> pubcookie-dev at u.washington.edu
More information about the pubcookie-dev