Closed
Bug 786239
Opened 12 years ago
Closed 11 years ago
Check identity fingerprints against DTLS fingerprints
Categories
(Core :: WebRTC: Networking, defect)
Core
WebRTC: Networking
Tracking
()
RESOLVED
DUPLICATE
of bug 884573
People
(Reporter: ekr, Unassigned)
Details
(Whiteboard: [WebRTC], [blocking-webrtc-])
We currently check the DTLS fingerprint against the DTLS channel, but not against the identity info. This bug is part of completing the identity work
|
||
Updated•12 years ago
|
Whiteboard: [WebRTC]
|
|
||
Updated•12 years ago
|
Whiteboard: [WebRTC] → [WebRTC], [blocking-webrtc+]
|
||
Comment 1•12 years ago
|
||
Not a blocker to preffing on
Whiteboard: [WebRTC], [blocking-webrtc+] → [WebRTC], [blocking-webrtc-]
|
||
Comment 2•11 years ago
|
||
Addressed in bug 884573. We don't accept a connection that doesn't match a=fingerprint and we don't surface identity information if the fingerprint in the identity assertion doesn't match all of the a=fingerprint values. Bug 942367 goes further and has setRemoteDescription fail if you want to guarantee a binding to a given peer identity.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•