ISSUE-43: Separate method for key agreement
Separate method for key agreement
- State:
- CLOSED
- Product:
- design for Web Crypto API
- Raised by:
- Richard Barnes
- Opened on:
- 2013-04-23
- Description:
- Adding to the tracker an issue that was raised on the mailing list;
<http://lists.w3.org/Archives/Public/public-webcrypto/2013Apr/0006.html> - Related Actions Items:
- No related actions
- Related emails:
- W3C Web Crypto WG - progressing on ISSUE-43 (from Virginie.GALINDO@gemalto.com on 2014-01-09)
- W3C Web Crypto WG - adhoc call on Key agreement/generation/derivation (from Virginie.GALINDO@gemalto.com on 2013-05-07)
- RE: W3C Web Crypto WG - 2 additionnal calls in May (from Virginie.GALINDO@gemalto.com on 2013-05-07)
- RE: W3C Web Crypto WG - 2 additionnal calls in May (from Michael.Hutchinson@gemalto.com on 2013-05-07)
- W3C Web Crypto WG - 2 additionnal calls in May (from Virginie.GALINDO@gemalto.com on 2013-05-06)
- W3C Web Crypto WG - Our next conference calls - correct dates, forget previous mail (from Virginie.GALINDO@gemalto.com on 2013-04-26)
- W3C Web Crypto WG - Our next conference calls (from Virginie.GALINDO@gemalto.com on 2013-04-26)
- crypto-ISSUE-43: Separate method for key agreement [design for Web Crypto API] (from sysbot+tracker@w3.org on 2013-04-23)
Related notes:
During the Web Crypto WG call on the 10th of feb 2014, we adressed this issue and decided that people who raised concern expressed acceptance with the API for deriveKey/deriveBits.
Virginie GALINDO, 13 Feb 2014, 09:01:43Display change log
