[wpkg-users] [Bug 102] New: registry checks fail if the value name contains backslashes

bugzilla-daemon at bugzilla.wpkg.org bugzilla-daemon at bugzilla.wpkg.org
Tue Feb 5 03:19:38 CET 2008


http://bugzilla.wpkg.org/show_bug.cgi?id=102

           Summary: registry checks fail if the value name contains
                    backslashes
           Product: WPKG
           Version: 0.9.10
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: wpkg.js
        AssignedTo: mangoo at wpkg.org
        ReportedBy: aross at whitley.unimelb.edu.au
         QAContact: wpkg-users at lists.wpkg.org


Both registry check conditions ("exists" and "equals") incorrectly fail when
the value name to be checked contains one or more backslashes (which are valid
characters in a value name, despite also being used as delimiters in key
names). 

An example of backslashes in value names can be found at
http://support.microsoft.com/kb/811660 , where value names such as
"\\*\*\*\*.dbf" and "\\Server\Share\*\*.*" are created under the key
"HKLM\Software\Microsoft\Windows\CurrentVersion\NetCache\ExclusionErrorSuppressionList".

The wpkg xml to check these registry entries in the usual fashion is:

<check type="registry" condition="exists"
path="HKLM\Software\Policies\Microsoft\Windows\NetCache\ExclusionErrorSuppressionList\\*\*\*\Cookies\index.dat"/>

or, if the value was important:

<check type="registry" condition="equals"
path="HKLM\Software\Policies\Microsoft\Windows\NetCache\ExclusionErrorSuppressionList\\*\*\*\Cookies\index.dat"
value="1"/>

However, both these checks will always fail, even when the values are present
(which can be confirmed through visual inspection using regedit, or from the
command-line with "reg query
HKLM\Software\Policies\Microsoft\Windows\NetCache\ExclusionErrorSuppressionList
/v \\*\*\*\Cookies\index.dat").

Within wpkg.js, the problem occurs in the function "getRegistryValue", but it
is actually the RegRead method of WScript.Shell that is to blame. See
http://www.tek-tips.com/viewthread.cfm?qid=786428&page=1 and
http://www.dbforums.com/showpost.php?s=65288675791938e7b13e1e52b96ef5ca&p=2929261&postcount=4


-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.



More information about the wpkg-users mailing list