Re: Calculation of a DH secret key
From: tlviewer (tlviewer_at_yahoo.com)
Date: 06/30/04
- Next message: Rhett Gong [MSFT]: "RE: Creating certificates with custom DN...."
- Previous message: tlviewer: "Re: Calculation of a DH secret key"
- In reply to: tlviewer: "Re: Calculation of a DH secret key"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 29 Jun 2004 19:29:30 -0700
tlviewer wrote:
> Nick wrote:
>
>> While using MS DSS and DH CSP for calculation of a DH secret key I've
>> obtained the following results.
>>
>> AlgId of imported BLOB AlgId of hPubKey Result
>>
>> AT_KEYEXCHANGE AT_SIGNATURE false (error 0x80090003
>> "Bad Key")
>> AT_KEYEXCHANGE AT_KEYEXCHANGE true
>> AT_SIGNATURE AT_SIGNATURE true
>> AT_SIGNATURE AT_KEYEXCHANGE true
>>
>> Is there anyone who can answer me the following question:
>> Why does the calculation fail for the first case?
>>
>> Please note that obtained results do not depend on a version of the
>> imported BLOB.
>>
>> Thanks,
>>
>> Nick
>
>
> Here is an open invitation to anyone that wants to
> negotiate a DH key exchange in this thread.
>
> (All numbers are in hex)
> len: 512 bits
> -----------
> prime =e7e98389fb552dec573f8f16719ecb1330c9ef725e86493df2a0bf6074656db1
> ab2da5d34b34338033a619901b9952d8cf47c144be55c01a3071e8ab74686bdd
>
> gen =bdc9022a154bbc6dcc205612736966b2902c3866616e3ee0f9e6b6ecf7333b1a
> eb8a044c2da2f022c180558e34425455ed74c5c8fb242aa454a22d0d23dbeb59
>
> y_pbk =65c79e8fda7686e573dbba7a57d298ce44225a3f34f1f142a4ad9d301da8febd
> d1e1e8e2b2a58ce1a67b769794d12699544142de565a7f340eb9adbab7708ea8
>
> I have saved my X value (random exponent). I have computed the above
> using the CryptoAPI.
>
> Import my (prime, gen) pair, get your KP_X, then import my
> y_pbk and export your y_pbk. Finish the calculation by hashing the
> session key. This will reflect the value of the shared secret (use SHA).
>
> Post your y_pbk here so I can complete my calculation of the shared
> secret. I will process multiple posts if need be. Each poster will
> arrive at a unique shared secret in partnership with the triplet posted
> above.
>
> Crypto anyone?
>
> regards,
> tlviewer
>
I left out one constraint:
get a 3DES session key
Alg = CALG_3DES;
... CryptSetKeyParam(hDHKey, KP_ALGID,(BYTE *) &Alg, (192 << 16) |
CRYPT_EXPORTABLE)
Did I leave anything else out?
cheers,
tlviewer
- Next message: Rhett Gong [MSFT]: "RE: Creating certificates with custom DN...."
- Previous message: tlviewer: "Re: Calculation of a DH secret key"
- In reply to: tlviewer: "Re: Calculation of a DH secret key"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
