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

[webrtc-pc] Certificate API: Do we need certificate introspection?

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Wed, 10 Feb 2016 09:40:04 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-132649451-1455097203-sysbot+gh@w3.org>
alvestrand has just created a new issue for 
https://github.com/w3c/webrtc-pc:

== Certificate API: Do we need certificate introspection? ==
At the moment, the certificate API we provide is this:

interface RTCCertificate {
    readonly        attribute DOMTimeStamp expires;
};

A question was raised on whether we could tell if a given cert was RSA
 or ECDSA - there doesn't seem to be one.

Would it be reasonable to require an introspection API that is able to
 tell something about it (possibly a subset of its keygen parameters)?

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/496 using your GitHub account
Received on Wednesday, 10 February 2016 09:40:10 UTC

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