Open
Bug 1177919
Opened 9 years ago
Updated 2 years ago
Expose the certificate that was used in RTCPeerConnection
Categories
(Core :: WebRTC: Signaling, defect, P4)
Core
WebRTC: Signaling
Tracking
()
NEW
| backlog | webrtc/webaudio+ |
People
(Reporter: mt, Unassigned)
References
Details
(Whiteboard: dev-doc-needed)
We have no visibility into what certificates are used for WebRTC at the application. Getting that visibility requires spec work. Different certificates per DTLS connection is possible, but it complicates the matter.
|
||
Updated•9 years ago
|
backlog: --- → webRTC+
Rank: 35
Priority: -- → P3
|
||
Comment 1•8 years ago
|
||
Presumably if/when this happens, it will require a doc update.
Whiteboard: dev-doc-needed
|
||
Comment 2•8 years ago
|
||
This is https://w3c.github.io/webrtc-pc/#dom-rtcdtlstransport-getremotecertificates correct?
|
||
Comment 3•7 years ago
|
||
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•