W3C home > Mailing lists > Public > public-webrtc@w3.org > December 2015

Re: setting generated key expire time.

From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 10 Dec 2015 10:09:18 +1100
Message-ID: <CABkgnnUwGOAbZmid68vxmqTfxfQ5+g5uG7FtjwiucA4R7sQR+w@mail.gmail.com>
To: Tim Panton <tim@phonefromhere.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
I had to add that for testing purposes, and I've since received a
number of requests to have it more properly defined.

https://github.com/w3c/webrtc-pc/pull/429

In creating this, I realize that this isn't exactly ideal.  Happy to
take comments.

On 10 December 2015 at 04:42, Tim Panton <tim@phonefromhere.com> wrote:
> I see that in the Firefox implementation
> peerConnection.generateCertificate() takes an expires parameter:
> Such that
>  var creq = mozRTCPeerConnection.generateCertificate(
> {name: "ECDSA", namedCurve: "P-256", expires: 365*24*60*60*1000*1000 })
> .then(function (s){ console.log(new Date(s.expires)); });
> creates a cert that is valid for a year.
>
> However, this isn’t described in the the current editors draft
> (https://w3c.github.io/webrtc-pc/#widl-RTCPeerConnection-generateCertificate-Promise-RTCCertificate--AlgorithmIdentifier-keygenAlgorithm)
> Am I missing something ?
>
> Tim.
>
Received on Wednesday, 9 December 2015 23:09:48 UTC

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