- From: <bugzilla@jessica.w3.org>
- Date: Mon, 09 Jun 2014 04:54:45 +0000
- To: public-webcrypto@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26011 --- Comment #1 from Ryan Sleevi <sleevi@google.com> --- > In addition, if you call importKey or generateKey, the resulting Key has an > algorithm attribute that does not expose the length of the key. This, > together with Bug 23159 and Bug 25094, seems to suggest we should just > promote length to KeyAlgorithm, and remove RsaKeyAlgorithm.modulusLength and > AesKeyAlgorithm.length. This would be a little redundant for EcKeyAlgorithm > and DhKeyAlgorithm, but that doesn't seem tragic. Please keep a single bug to report. That way discussions about why I strongly disagree about length as a generic property can be discussed :) As it relates to PBKDF2, I don't think a .length() property makes sense. It doesn't provide a signal for effective strength (as it does for other key types), nor is it a reasonable proxy for entropy. That said, if you still feel otherwise, please file another bug. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Monday, 9 June 2014 04:54:46 UTC