http://bugs.winehq.org/show_bug.cgi?id=11070
--- Comment #19 from Mark Smith mhs@hp.com 2010-05-24 14:00:13 --- Windows/IE has a certificate manager which can be invoked with a combination of natives:
mhs@pisa:~/ie7dlls$ for i in cryptui.dll crypt32.dll cryptnet.dll msasn1.dll rsaenh.dll secur32.dll userenv.dll ; do cp ./$i ~/.wine/drive_c/windows/system32/ ; wine regsvr32 C:\windows\system32\$i ; done mhs@pisa:~/ie7dlls$ cd ~/.wine/drive_c/windows/system32/
mhs@pisa:~/.wine/drive_c/windows/system32$ WINEDLLOVERRIDES=msasn1,secur32,userenv,cryptui,cryptnet,crypt32,rsaenh=n,b wine rundll32.exe cryptui.dll,CryptUIStartCertMgr
It gets as far as a pop-up about a cryptographic "service provider" not being installed. On the terminal, an advapi error can be seen during execution of rsaenh.dll. On a Windows system, this would be where the actual work of "importing" the certificate in a Windows system. See Dependency Walker attachment for Windows details.
ImportPFX will fail in almost exactly the same way with this combination of natives.
As of wine-1.2-rc1