Winetest.exe could mess up your secured wireless access on Windows

[Paul Vriens]

Hi,

If you never run winetest you can skip this email but shame on you ;)

It turns out that one of the advapi32 tests messes up the registry, or 
to be more correct doesn't restore an original value. This bug has been 
present since the introduction of these specific tests in 2004.

This means that once you've run winetest on a Windows 2000 or higher box 
one of the values in the registry prevents you from connecting to a 
secured wireless access point (problem reproduced on Vista and Windows 
7). There could be more cryptographic related problems due to this bug 
but these haven't surfaced yet.

A patch has been submitted to fix this for new test runs but it won't 
fix the current situation.

If you experience this issue after running winetest you need to change a 
value in the registry. This can be done manually by changing the "Name" 
value at 
"HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Defaults\Provider 
Types\Type 001" from "Microsoft Base Cryptographic Provider v1.0" to 
"Microsoft Strong Cryptographic Provider".

-- 
Cheers,

Paul.