[pubcookie-dev] Windows 2k3 3.3.0a registry problems

[Phil Jochimsen]

Nathan,

Thanks for the info. You are correct, this is not a showstopper, as 
protection on a directory that doesn't exist, well, doesn't matter. ;) 
It does make the registry look like hell though, as the how deep the 
directory is that was changed is how deep the extra keys go (5 dir's 
deep mean 5 extra lvls of reg keys, total of 10 lvls of reg keys).

Thanks,

Phil Jochimsen
Web Technologist
DoIT-EIS-IIAT
UW Madison


Nathan Dors wrote:

> 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:
>
> http://www.pubcookie.org/docs/install-filter.html#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 bug.
>
> -Nathan
>
> On Tue, 9 May 2006, PHILIP D JOCHIMSEN wrote:
>
>> Well, I have managed to find another interesting dilemma: extra
>> registry
>> keys & entries, like below.
>>
>> Actual directory structure:
>> /root
>> /root/protected
>> /root/protected/error
>> /root/protected/logout
>>
>> Structure recorded in the registry:
>> /root
>> /root/protected
>> /root/protected/error
>> /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
>> /root/protected/logout/logout    **no actual config info**
>>
>> It certainly appears to be a corruption of logic when changing the
>> appID
>> 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
>> something
>> 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
>> that
>> "ok" doesn't realize has already been done?
>>
>> Has anyone else seen this before?
>>
>> Thanks,
>>
>> Phil Jochimsen
>> Web Technologist
>> DoIT-EIS-IIAT
>> UW Madison
>> _______________________________________________
>> pubcookie-dev mailing list
>> pubcookie-dev at u.washington.edu
>> http://mailman1.u.washington.edu/mailman/listinfo/pubcookie-dev
>>
>