After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 123674 - xmlsec-mscrypto: actual AES crypto provider name is different from one defined by Microsoft
xmlsec-mscrypto: actual AES crypto provider name is different from one define...
Status: RESOLVED FIXED
Product: xmlsec
Classification: Other
Component: general
1.2.1
Other Linux
: Normal normal
: ---
Assigned To: Aleksey Sanin
Aleksey Sanin
Depends on:
Blocks:
 
 
Reported: 2003-10-02 01:47 UTC by Aleksey Sanin
Modified: 2010-04-26 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Aleksey Sanin 2003-10-02 01:47:05 UTC 
The Windows Platform SDK has AES crypto provider name define
MS_ENH_RSA_AES_PROV equal to "Microsoft Enhanced RSA and AES Cryptographic
Provider". However, the real AES crypto provider name is slightly different
and is equal to "Microsoft Enhanced RSA and AES Cryptographic Provider".
Probably the code needs to be changed to either always use the "official"
name (if MS would change the actual name) or to check both names.
Comment 1 Aleksey Sanin 2003-10-03 19:49:53 UTC 
Correction from Wouter:

The actual current name is mentioned wrongly in this bug report, the
name is currently:

   "Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype)"

while it should be according to msdn documentation:
   
    "Microsoft Enhanced RSA and AES Cryptographic Provider"
Comment 2 Jean-Marc Desperrier 2005-04-11 15:09:13 UTC 
In fact, both names exist.

The '(Prototype)' version is the one under XP SP1 and SP2, and the other the one
under Server 2003.

The Server 2003 version is able to do SHA-256 and SHA-384, but the XP version is
not.
Comment 3 Aleksey Sanin 2010-04-26 21:47:46 UTC 
Fixed the code to lookup both names at runtime