ISSUE-36: Semantics for key generation versus key derivation

derivation

Semantics for key generation versus key derivation

State:
CLOSED
Product:
crypto for Web Crypto API
Raised by:
Ryan Sleevi
Opened on:
2012-08-28
Description:
The distinction between deriveKey and generateKey is not currently well-defined. For purposes of understanding where future algorithm definitions should go, it would be helpful to know what the expected (generic) inputs and outputs are for both methods.

Does deriveKey only yield symmetric keys? Are the keys of a particular type (eg: a Key object with an associated algorithm), or are they simply a series of bytes (eg: an ArrayBuffer)?
Related Actions Items:
Related emails:
  1. RE: W3C Web Crypto WG - progressing on ISSUE-36 (from Vijay.Bharadwaj@microsoft.com on 2014-03-03)
  2. RE: W3C Web Crypto WG - progressing on ISSUE-36 (from Vijay.Bharadwaj@microsoft.com on 2014-02-24)
  3. RE: W3C Web Crypto WG - progressing on ISSUE-36 (from Virginie.GALINDO@gemalto.com on 2014-01-20)
  4. RE: W3C Web Crypto WG - progressing on ISSUE-36 (from Vijay.Bharadwaj@microsoft.com on 2014-01-14)
  5. W3C Web Crypto WG - progressing on ISSUE-36 (from Virginie.GALINDO@gemalto.com on 2014-01-09)
  6. ISSUE-36: Semantics for key generation versus key derivation (from Vijay.Bharadwaj@microsoft.com on 2013-11-14)
  7. W3C Web Crypto WG - adhoc call on Key agreement/generation/derivation (from Virginie.GALINDO@gemalto.com on 2013-05-07)
  8. RE: W3C Web Crypto WG - 2 additionnal calls in May (from Virginie.GALINDO@gemalto.com on 2013-05-07)
  9. RE: W3C Web Crypto WG - 2 additionnal calls in May (from Michael.Hutchinson@gemalto.com on 2013-05-07)
  10. W3C Web Crypto WG - 2 additionnal calls in May (from Virginie.GALINDO@gemalto.com on 2013-05-06)
  11. W3C Web Crypto WG - Our next conference calls - correct dates, forget previous mail (from Virginie.GALINDO@gemalto.com on 2013-04-26)
  12. W3C Web Crypto WG - Our next conference calls (from Virginie.GALINDO@gemalto.com on 2013-04-26)
  13. Re: baseKey argument to createKeyDeriver (from sleevi@google.com on 2012-10-29)
  14. W3C WebCrypto meeting minutes (from hhalpin@w3.org on 2012-09-24)
  15. Re: W3C Web Crypto WG - agenda for 24th of september call - today (from hhalpin@w3.org on 2012-09-24)
  16. W3C Web Crypto WG - agenda for 24th of september call - today (from Virginie.GALINDO@gemalto.com on 2012-09-24)
  17. W3C Web Crypto - classifying issues - a new proposal (from Virginie.GALINDO@gemalto.com on 2012-09-22)
  18. Re: W3C Web Crypto - classifying issues - a new proposal (from sleevi@google.com on 2012-09-21)
  19. RE: W3C Web Crypto - classifying issues - a new proposal (from Virginie.GALINDO@gemalto.com on 2012-09-21)
  20. RE: New Editor's Draft Published (from karen.lu@gemalto.com on 2012-09-04)
  21. RE: crypto-ISSUE-37: Method naming [Web Cryptography API] (from Vijay.Bharadwaj@microsoft.com on 2012-09-04)
  22. RE: (Minor) New version published (from Vijay.Bharadwaj@microsoft.com on 2012-09-04)
  23. New Editor's Draft Published (from sleevi@google.com on 2012-08-31)
  24. Re: (Minor) New version published (from sleevi@google.com on 2012-08-31)
  25. RE: (Minor) New version published (from Vijay.Bharadwaj@microsoft.com on 2012-08-28)
  26. Re: (Minor) New version published (from sleevi@google.com on 2012-08-28)
  27. crypto-ISSUE-36 (derivation): Semantics for key generation versus key derivation [Web Cryptography API] (from sysbot+tracker@w3.org on 2012-08-28)

Related notes:

Following recent exchanges, the last specification proposal answers that issue. Issues is closed.

Virginie GALINDO, 20 Jan 2014, 13:38:58

Display change log ATOM feed


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 36.html,v 1.1 2017/02/13 16:16:51 ted Exp $