Status of CryptoAPI and advapi32 in Wine?
yes_this_is_a_real_address at earthlink.net
Mon Mar 22 15:38:23 CST 2004
I'm trying to get all major functionality of an application, eMule, to work
under Wine. eMule uses the following crypto-related imports:
Some of these, ie, CryptAcquireContextA(), when called in turn make calls to
CryptoAPI. It seems CryptoAPI isn't implemented fully in Wine yet because
eMule is unable to (indirectly) utilize CryptoAPI's simple RSA services.
I've tried using the native Win98 and XP advapi32.dll without success, and
also tried using the WinXP native rsaenh.dll along with the following fake
\Microsoft Base Cryptographic Provider v1.0]
\Microsoft Strong Cryptographic Provider]
"Name"="Microsoft Strong Cryptographic Provider"
"TypeName"="RSA Full (Signature and Key Exchange)"
(The GUID came from a patch I found which was submitted to WineX CVS.)
rsabase.dll likewise doesn't work.
I'm unsure as to what more should be done to make valid CSPs available through
CryptoAPI/advapi32 to my Wine applications. All I need to get working for
eMule is RSA, but DSS would be nice to have also (though I haven't tested DSS
What is the current status of CryptoAPI and advapi32 emulation?
I read that someone is working on tying CryptoAPI to libgcrypt. What is the
status of that?
More information about the wine-users