Closed Bug 798943 Opened 13 years ago Closed 11 years ago

Prefer (require?) PFS cipher suites for DTLS-SRTP

Categories

(Core :: WebRTC: Networking, defect, P3)

Product:
Core
Component:
WebRTC: Networking
Platform:
x86
macOS
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1052610

People

(Reporter: ekr, Assigned: ekr)

References

Details

(Whiteboard: [WebRTC] [blocking-webrtc-])

We should prefer PFS cipher suites.
Whiteboard: [WebRTC] [blocking-webrtc+]
Does this really block preffing on?
Assignee: nobody → ekr
Priority: -- → P3
Flags: needinfo?(ekr)
I don't think it blocks preffing on. I believe we already choose them
Flags: needinfo?(ekr)
Whiteboard: [WebRTC] [blocking-webrtc+] → [WebRTC] [blocking-webrtc-]
(In reply to Eric Rescorla (:ekr) from comment #0) > We should prefer PFS cipher suites. This seems like a reasonable idea. But, I am curious about the reasoning. Is there a particular reason that PFS is especially important for DTLS-SRTP?
Martin, this is fixed, right?
Flags: needinfo?(martin.thomson)
I think so, but we were blocked on chrome. See bug 996237 for the original; but I can't find the chromium bug (which should have landed).
Depends on: 996237
Bug 1052610 has already landed the code for this. Now that Chrome finally supports ECDHE properly, we can remove the #ifdef 0 guards.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(martin.thomson)
Resolution: --- → DUPLICATE
Oh, and I should note, that change *requires* PFS, it's not a mere preference (something we have from NSS anyway).
You need to log in before you can comment on or make changes to this bug.