W3C home > Mailing lists > Public > public-webrtc@w3.org > October 2016

[webrtc-pc] Further generateCertificate changes required

From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
Date: Thu, 27 Oct 2016 19:17:09 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-185756302-1477595827-sysbot+gh@w3.org>
foolip has just created a new issue for 
https://github.com/w3c/webrtc-pc:

== Further generateCertificate changes required ==
A follow-up to https://github.com/w3c/webrtc-pc/issues/879 and 
https://github.com/w3c/webrtc-pc/pull/880:

A WebIDL dictionary doesn't allow for anything "extra", so using the 
`RTCGenerateCertificateOptions` dictionary, the only possible members 
would be `name` and `expires`. But the spec requires at least these 
things to work:
* `{ name: "RSASSA-PKCS1-v1_5", modulusLength: 2048, publicExponent: 
new Uint8Array([1, 0, 1]), hash: "SHA-256" }`
* `{ name: "ECDSA", namedCurve: "P-256" }`

The [algorithm normalization 
process](https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html#algorithm-normalization)
 link is stale, but must mean that [normalize an 
algorithm](https://w3c.github.io/webcrypto/Overview.html#dfn-normalize-an-algorithm)
 should be used, which requires an `AlgorithmIdentifier` as its input.
 That's how it's implemented (@henbos) in Blink. (The prose for 
`generateCertificate` still refers to `AlgorithmIdentifier`, but 
that's an oversight I think.)

Paging @ericroman920 and @mwatson2 for advice on how to do this.

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/891 using your GitHub account
Received on Thursday, 27 October 2016 19:17:15 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:49 UTC