http://bugs.winehq.org/show_bug.cgi?id=21938
--- Comment #18 from Paul Vriens Paul.Vriens.Wine@gmail.com 2010-03-08 02:26:40 --- Ran a diff on before and after registry settings. Don't know which test messes this up but the fix (to get secured wireless back) is to edit the registry.
Change the data for 'Name' at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Defaults\Provider Types\Type 001
from 'Microsoft Base Cryptographic Provider v1.0' to 'Microsoft Strong Cryptographic Provider'
My first suspect is the advapi32:crypt tests btw. As we now only have to look for tests that change the above value we can use VM's (much easier testing).