Re: Converting Diffie-Hellman Session keys to CALG_AES_128
- From: joe hacker <tlviewer@xxxxxxxxx>
- Date: Mon, 18 Sep 2006 23:04:17 -0700
On Mon, 18 Sep 2006 11:51:15 -0700, Medical-Fix wrote:
Hey Joe thansk for the help.
I tryed your change but I get the following
error code: 0x80090008
//what I used
ALG_ID Algid = CALG_AES_128;
CryptSetKeyParam(hSessionKey, KP_ALGID, (PBYTE)&Algid,
(128<<16)|CRYPT_EXPORTABLE);
//
let me know what you think...
In order to use AES you need to be on WinXP or higher and then
you need to use the dedicated AES provider. I didn't stop to consider that
the PROV_DSS_DH provider still only supports RC4, 3DES, etc, but not AES,
no matter what OS it runs on.
I'd be surprised if you can use CALG_AES_128 in DH.
regards,
tlviewer
.
- References:
- Converting Diffie-Hellman Session keys to CALG_AES_128
- From: Medical-Fix
- Re: Converting Diffie-Hellman Session keys to CALG_AES_128
- From: joe hacker
- Re: Converting Diffie-Hellman Session keys to CALG_AES_128
- From: Medical-Fix
- Converting Diffie-Hellman Session keys to CALG_AES_128
- Prev by Date: CSP and how to use a public key from a certificate to cipher data
- Next by Date: RE: Tcp Port 3367 Established
- Previous by thread: Re: Converting Diffie-Hellman Session keys to CALG_AES_128
- Next by thread: Windows Service Created Sub-process?
- Index(es):