Open Bug 1177919 Opened 6 years ago Updated 4 years ago

Expose the certificate that was used in RTCPeerConnection

Categories

(Core :: WebRTC: Signaling, defect, P4)

defect

Tracking

()

Blocking Flags:

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.
backlog: --- → webRTC+
Rank: 35
Priority: -- → P3
Presumably if/when this happens, it will require a doc update.
Whiteboard: dev-doc-needed
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
You need to log in before you can comment on or make changes to this bug.