Closed Bug 1275252 Opened 8 years ago Closed 8 years ago

Deal with TLS 1.3 intolerance

Categories

(Core :: Security: PSM, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla49
Tracking Status
firefox49 --- fixed

People

(Reporter: emk, Assigned: emk)

References

Details

(Whiteboard: [psm-assigned])

Attachments

(1 file)

Attached patch patchSplinter Review
- Added SSL_ERROR_INTERNAL_ERROR_ALERT to fallback reasons. - Do not send the fallback SCSV with TLS 1.2. The fallback SCSV spec (RFC 7507) explicitly allows this: https://tools.ietf.org/html/rfc7507 > For example, during the initial > deployment of a new protocol version (when some interoperability > problems may have to be expected), smoothly falling back to the > previous protocol version in case of problems may be preferable to > potentially not being able to connect at all: so TLS_FALLBACK_SCSV > could be omitted for this particular protocol downgrade step. Also, TLS 1.3 has a built-in anti-downgrade mechanism to prevent downgrade attacks. So fallback SCSV is unnecessary. Microsoft opposed the fallback SCSV because they concerned that the fallback SCSV might break forward compatibility. And they were right :(
Attachment #8755836 - Flags: review?(dkeeler)
Assignee: nobody → VYV03354
Whiteboard: [psm-assigned]
Comment on attachment 8755836 [details] [diff] [review] patch Review of attachment 8755836 [details] [diff] [review]: ----------------------------------------------------------------- I guess I'm not too surprised there are issues with this. r=me
Attachment #8755836 - Flags: review?(dkeeler) → review+
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla49
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: