From: SourceForge.net <no...@so...> - 2004-07-30 22:07:21
|
Patches item #1000966, was opened at 2004-07-30 16:07 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=302435&aid=1000966&group_id=2435 Category: w32api Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ed Schaller (schallee) Assigned to: Nobody/Anonymous (nobody) Summary: Missing Crypto API types and defines (AES & HMAC) Initial Comment: BLOBHEADER: ----------- Typdef for _PUBLICKEYSTRUC which is defined already. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/blobheader.asp AES defines for algorithms and providers: ----------------------------------------- The defines for CALG_AES* depend on the ALG_SID_AES*. ALG_SID_AES* seem to be undocumented on msdn (at least the search for them returns nothing although we all know how useful msdn's search is). Also, MS_ENH_RSA_AES_PROV according to Microsoft is "Microsoft Enhanced RSA and AES Cryptographic Provider". It may be that in win2003 server (which I do not have access to) but it is certainly not in winxp. I have defined it in the patch to be "Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype)" which is what it is defined as in winxp. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/microsoft_aes_cryptographic_provider.asp HMAC_INFO HP_HMAC_INFO: ----------------------- Used to do HMACs. Not that MS's implementation is usable for me (key has to be a symmetric session key of a symmetric algorithm and therefore is limited in it's possible sizes). I have a hmac implementation that uses MS's hashes if anyone wants it. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/hmac_info.asp CALG_SHA1: ---------- Same as CALG_SHA. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/cryptcreatehash.asp ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=302435&aid=1000966&group_id=2435 |
From: SourceForge.net <no...@so...> - 2004-08-02 09:49:05
|
Patches item #1000966, was opened at 2004-07-31 10:07 Message generated for change (Comment added) made by dannysmith You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=302435&aid=1000966&group_id=2435 Category: w32api Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ed Schaller (schallee) Assigned to: Nobody/Anonymous (nobody) Summary: Missing Crypto API types and defines (AES & HMAC) Initial Comment: BLOBHEADER: ----------- Typdef for _PUBLICKEYSTRUC which is defined already. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/blobheader.asp AES defines for algorithms and providers: ----------------------------------------- The defines for CALG_AES* depend on the ALG_SID_AES*. ALG_SID_AES* seem to be undocumented on msdn (at least the search for them returns nothing although we all know how useful msdn's search is). Also, MS_ENH_RSA_AES_PROV according to Microsoft is "Microsoft Enhanced RSA and AES Cryptographic Provider". It may be that in win2003 server (which I do not have access to) but it is certainly not in winxp. I have defined it in the patch to be "Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype)" which is what it is defined as in winxp. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/microsoft_aes_cryptographic_provider.asp HMAC_INFO HP_HMAC_INFO: ----------------------- Used to do HMACs. Not that MS's implementation is usable for me (key has to be a symmetric session key of a symmetric algorithm and therefore is limited in it's possible sizes). I have a hmac implementation that uses MS's hashes if anyone wants it. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/hmac_info.asp CALG_SHA1: ---------- Same as CALG_SHA. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/cryptcreatehash.asp ---------------------------------------------------------------------- >Comment By: Danny Smith (dannysmith) Date: 2004-08-02 21:49 Message: Logged In: YES user_id=11494 Thanks Please have a look at the Changlog and submit a changelog entry in that style. Danny ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=302435&aid=1000966&group_id=2435 |
From: SourceForge.net <no...@so...> - 2004-08-03 16:50:23
|
Patches item #1000966, was opened at 2004-07-30 16:07 Message generated for change (Comment added) made by schallee You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=302435&aid=1000966&group_id=2435 Category: w32api Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ed Schaller (schallee) Assigned to: Nobody/Anonymous (nobody) Summary: Missing Crypto API types and defines (AES & HMAC) Initial Comment: BLOBHEADER: ----------- Typdef for _PUBLICKEYSTRUC which is defined already. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/blobheader.asp AES defines for algorithms and providers: ----------------------------------------- The defines for CALG_AES* depend on the ALG_SID_AES*. ALG_SID_AES* seem to be undocumented on msdn (at least the search for them returns nothing although we all know how useful msdn's search is). Also, MS_ENH_RSA_AES_PROV according to Microsoft is "Microsoft Enhanced RSA and AES Cryptographic Provider". It may be that in win2003 server (which I do not have access to) but it is certainly not in winxp. I have defined it in the patch to be "Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype)" which is what it is defined as in winxp. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/microsoft_aes_cryptographic_provider.asp HMAC_INFO HP_HMAC_INFO: ----------------------- Used to do HMACs. Not that MS's implementation is usable for me (key has to be a symmetric session key of a symmetric algorithm and therefore is limited in it's possible sizes). I have a hmac implementation that uses MS's hashes if anyone wants it. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/hmac_info.asp CALG_SHA1: ---------- Same as CALG_SHA. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/cryptcreatehash.asp ---------------------------------------------------------------------- >Comment By: Ed Schaller (schallee) Date: 2004-08-03 10:50 Message: Logged In: YES user_id=2001 Ok, I've added to the changelog and created a new patch. The patch is against cvs btw. I hope that the format is right. GNU isn't exactly very informative on the exact format. ---------------------------------------------------------------------- Comment By: Danny Smith (dannysmith) Date: 2004-08-02 03:49 Message: Logged In: YES user_id=11494 Thanks Please have a look at the Changlog and submit a changelog entry in that style. Danny ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=302435&aid=1000966&group_id=2435 |
From: SourceForge.net <no...@so...> - 2004-08-04 00:24:05
|
Patches item #1000966, was opened at 2004-07-31 10:07 Message generated for change (Comment added) made by dannysmith You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=302435&aid=1000966&group_id=2435 Category: w32api Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ed Schaller (schallee) Assigned to: Nobody/Anonymous (nobody) Summary: Missing Crypto API types and defines (AES & HMAC) Initial Comment: BLOBHEADER: ----------- Typdef for _PUBLICKEYSTRUC which is defined already. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/blobheader.asp AES defines for algorithms and providers: ----------------------------------------- The defines for CALG_AES* depend on the ALG_SID_AES*. ALG_SID_AES* seem to be undocumented on msdn (at least the search for them returns nothing although we all know how useful msdn's search is). Also, MS_ENH_RSA_AES_PROV according to Microsoft is "Microsoft Enhanced RSA and AES Cryptographic Provider". It may be that in win2003 server (which I do not have access to) but it is certainly not in winxp. I have defined it in the patch to be "Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype)" which is what it is defined as in winxp. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/microsoft_aes_cryptographic_provider.asp HMAC_INFO HP_HMAC_INFO: ----------------------- Used to do HMACs. Not that MS's implementation is usable for me (key has to be a symmetric session key of a symmetric algorithm and therefore is limited in it's possible sizes). I have a hmac implementation that uses MS's hashes if anyone wants it. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/hmac_info.asp CALG_SHA1: ---------- Same as CALG_SHA. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/cryptcreatehash.asp ---------------------------------------------------------------------- >Comment By: Danny Smith (dannysmith) Date: 2004-08-04 12:23 Message: Logged In: YES user_id=11494 You wrote: Also MS_ENH_RSA_AES_PROV according to Microsoft is "Microsoft Enhanced RSA and AES Cryptographic Provider". It may be that in win2003 server (which I do not have access to) but it is certainly not in winxp. I have defined it in the patch to be "Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype)" which is what it is defined as in winxp I would prefer to use the documented string in header. Do you have evidence that the documented define breaks anything? Danny ---------------------------------------------------------------------- Comment By: Ed Schaller (schallee) Date: 2004-08-04 04:50 Message: Logged In: YES user_id=2001 Ok, I've added to the changelog and created a new patch. The patch is against cvs btw. I hope that the format is right. GNU isn't exactly very informative on the exact format. ---------------------------------------------------------------------- Comment By: Danny Smith (dannysmith) Date: 2004-08-02 21:49 Message: Logged In: YES user_id=11494 Thanks Please have a look at the Changlog and submit a changelog entry in that style. Danny ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=302435&aid=1000966&group_id=2435 |
From: SourceForge.net <no...@so...> - 2004-08-04 16:58:03
|
Patches item #1000966, was opened at 2004-07-30 16:07 Message generated for change (Comment added) made by schallee You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=302435&aid=1000966&group_id=2435 Category: w32api Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ed Schaller (schallee) Assigned to: Nobody/Anonymous (nobody) Summary: Missing Crypto API types and defines (AES & HMAC) Initial Comment: BLOBHEADER: ----------- Typdef for _PUBLICKEYSTRUC which is defined already. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/blobheader.asp AES defines for algorithms and providers: ----------------------------------------- The defines for CALG_AES* depend on the ALG_SID_AES*. ALG_SID_AES* seem to be undocumented on msdn (at least the search for them returns nothing although we all know how useful msdn's search is). Also, MS_ENH_RSA_AES_PROV according to Microsoft is "Microsoft Enhanced RSA and AES Cryptographic Provider". It may be that in win2003 server (which I do not have access to) but it is certainly not in winxp. I have defined it in the patch to be "Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype)" which is what it is defined as in winxp. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/microsoft_aes_cryptographic_provider.asp HMAC_INFO HP_HMAC_INFO: ----------------------- Used to do HMACs. Not that MS's implementation is usable for me (key has to be a symmetric session key of a symmetric algorithm and therefore is limited in it's possible sizes). I have a hmac implementation that uses MS's hashes if anyone wants it. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/hmac_info.asp CALG_SHA1: ---------- Same as CALG_SHA. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/cryptcreatehash.asp ---------------------------------------------------------------------- >Comment By: Ed Schaller (schallee) Date: 2004-08-04 10:58 Message: Logged In: YES user_id=2001 Yes, there is such evidence. I can write some sample test cases if you would like. If you use the documented string it will not work in XP. I'm not sure what the best way to do this would be. The AES CSP does not exist in any version other than XP and 2003 server. If you follow the documentation, it will not function in XP. I can only hope that it does in 2003 server. How about a solution like this: #define MS_ENH_RSA_AES_PROV_XP ... #define MS_ENH_RSA_AES_PROV_2003 ... #define MS_ENH_RSA_AES_PROV MS_ENH_RSA_AES_PROV_2003 That way the default case will follow the docs, but the other cases are still availible if desired and can be tested for with a #ifdef. I don't really know what the policy is when the documentation is wrong/insufficient. ---------------------------------------------------------------------- Comment By: Danny Smith (dannysmith) Date: 2004-08-03 18:23 Message: Logged In: YES user_id=11494 You wrote: Also MS_ENH_RSA_AES_PROV according to Microsoft is "Microsoft Enhanced RSA and AES Cryptographic Provider". It may be that in win2003 server (which I do not have access to) but it is certainly not in winxp. I have defined it in the patch to be "Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype)" which is what it is defined as in winxp I would prefer to use the documented string in header. Do you have evidence that the documented define breaks anything? Danny ---------------------------------------------------------------------- Comment By: Ed Schaller (schallee) Date: 2004-08-03 10:50 Message: Logged In: YES user_id=2001 Ok, I've added to the changelog and created a new patch. The patch is against cvs btw. I hope that the format is right. GNU isn't exactly very informative on the exact format. ---------------------------------------------------------------------- Comment By: Danny Smith (dannysmith) Date: 2004-08-02 03:49 Message: Logged In: YES user_id=11494 Thanks Please have a look at the Changlog and submit a changelog entry in that style. Danny ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=302435&aid=1000966&group_id=2435 |
From: SourceForge.net <no...@so...> - 2004-08-11 07:54:21
|
Patches item #1000966, was opened at 2004-07-31 10:07 Message generated for change (Comment added) made by dannysmith You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=302435&aid=1000966&group_id=2435 Category: w32api Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ed Schaller (schallee) Assigned to: Nobody/Anonymous (nobody) Summary: Missing Crypto API types and defines (AES & HMAC) Initial Comment: BLOBHEADER: ----------- Typdef for _PUBLICKEYSTRUC which is defined already. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/blobheader.asp AES defines for algorithms and providers: ----------------------------------------- The defines for CALG_AES* depend on the ALG_SID_AES*. ALG_SID_AES* seem to be undocumented on msdn (at least the search for them returns nothing although we all know how useful msdn's search is). Also, MS_ENH_RSA_AES_PROV according to Microsoft is "Microsoft Enhanced RSA and AES Cryptographic Provider". It may be that in win2003 server (which I do not have access to) but it is certainly not in winxp. I have defined it in the patch to be "Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype)" which is what it is defined as in winxp. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/microsoft_aes_cryptographic_provider.asp HMAC_INFO HP_HMAC_INFO: ----------------------- Used to do HMACs. Not that MS's implementation is usable for me (key has to be a symmetric session key of a symmetric algorithm and therefore is limited in it's possible sizes). I have a hmac implementation that uses MS's hashes if anyone wants it. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/hmac_info.asp CALG_SHA1: ---------- Same as CALG_SHA. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/cryptcreatehash.asp ---------------------------------------------------------------------- >Comment By: Danny Smith (dannysmith) Date: 2004-08-11 19:54 Message: Logged In: YES user_id=11494 Applied. I modified by making the MS_ENH_RSA_AES_PROV define conditional on _WIN32_WINNT. Thanks Danny ---------------------------------------------------------------------- Comment By: Ed Schaller (schallee) Date: 2004-08-05 04:58 Message: Logged In: YES user_id=2001 Yes, there is such evidence. I can write some sample test cases if you would like. If you use the documented string it will not work in XP. I'm not sure what the best way to do this would be. The AES CSP does not exist in any version other than XP and 2003 server. If you follow the documentation, it will not function in XP. I can only hope that it does in 2003 server. How about a solution like this: #define MS_ENH_RSA_AES_PROV_XP ... #define MS_ENH_RSA_AES_PROV_2003 ... #define MS_ENH_RSA_AES_PROV MS_ENH_RSA_AES_PROV_2003 That way the default case will follow the docs, but the other cases are still availible if desired and can be tested for with a #ifdef. I don't really know what the policy is when the documentation is wrong/insufficient. ---------------------------------------------------------------------- Comment By: Danny Smith (dannysmith) Date: 2004-08-04 12:23 Message: Logged In: YES user_id=11494 You wrote: Also MS_ENH_RSA_AES_PROV according to Microsoft is "Microsoft Enhanced RSA and AES Cryptographic Provider". It may be that in win2003 server (which I do not have access to) but it is certainly not in winxp. I have defined it in the patch to be "Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype)" which is what it is defined as in winxp I would prefer to use the documented string in header. Do you have evidence that the documented define breaks anything? Danny ---------------------------------------------------------------------- Comment By: Ed Schaller (schallee) Date: 2004-08-04 04:50 Message: Logged In: YES user_id=2001 Ok, I've added to the changelog and created a new patch. The patch is against cvs btw. I hope that the format is right. GNU isn't exactly very informative on the exact format. ---------------------------------------------------------------------- Comment By: Danny Smith (dannysmith) Date: 2004-08-02 21:49 Message: Logged In: YES user_id=11494 Thanks Please have a look at the Changlog and submit a changelog entry in that style. Danny ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=302435&aid=1000966&group_id=2435 |