[Bug 26011] New: Add importKey/generateKey marks and key length for PBKDF2

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

            Bug ID: 26011
           Summary: Add importKey/generateKey marks and key length for
                    PBKDF2
           Product: Web Cryptography
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Web Cryptography API Document
          Assignee: sleevi@google.com
          Reporter: rlb@ipv.sx
                CC: public-webcrypto@w3.org

The algorithm/method table does not have a check mark for PBKDF2 in the
generateKey or importKey methods.
https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html#algorithms-index

But the PBKDF2 section has definitions for generateKey and importKey.
https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html#pbkdf2

The right solution here is to add the check marks, I think.  

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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Saturday, 7 June 2014 22:01:08 UTC