RE: Support optional private value length for DH PKCS#3 ?

I've never seen that used in practice, and the approach of defining q tends to be more commonly used (e.g. SP800-56A doesn't mention l at all). I would prefer to not introduce it at all.

From: Mark Watson [mailto:watsonm@netflix.com]
Sent: Tuesday, February 25, 2014 8:32 AM
To: public-webcrypto@w3.org
Subject: Support optional private value length for DH PKCS#3 ?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24804


PKCS#3 defined an optional parameter, l, which specifies the private value length.



Should we expose this in the WebCrypto API ?

...Mark

Received on Tuesday, 25 February 2014 17:25:05 UTC