W3C home > Mailing lists > Public > public-webcrypto@w3.org > April 2014

[Bug 25468] "CONCAT" KDF only supports deriveBits, not deriveKey

From: <bugzilla@jessica.w3.org>
Date: Fri, 25 Apr 2014 23:09:07 +0000
To: public-webcrypto@w3.org
Message-ID: <bug-25468-7213-B5W6MWTE0N@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25468

Mark Watson <watsonm@netflix.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |watsonm@netflix.com

--- Comment #1 from Mark Watson <watsonm@netflix.com> ---
This is a point of confusion that we've discussed before. I guess some
clarification is needed in the specification.

Whilst there are both a deriveKey and deriveBits *methods* there is no 'derive
key' *operation*. The procedure for the deriveKey method uses the same 'derive
bits' operation as the procedure for the deriveBits *method*. The difference is
that in the deriveKey case the returned bits are fed into the import key
operation of the appropriate target algorithm wheras for the deriveBits
operation the bits are returned directly.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 25 April 2014 23:09:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:17:22 UTC