status-firefox56: --- → affected
tracking-firefox56: --- → blocking
This is a reminder that the pref should be disabled before 56 goes to release, because we don't have a way to automatically flip a pref between beta and release.
Note, the patch should be the same as for bug 1385927. Do we need to attach a separate patch for this bug?
Created attachment 8906948 [details] [diff] [review] patch for 56 We can just graft over the changeset from 55 when 56 merges to release and just update the commit message, like this.
Assignee: nobody → jcristau
Attachment #8906948 - Flags: review+
woops didn't mean to self-assign.
Assignee: jcristau → nobody
Ekr, is it OK if we uplift this now and disable for beta 12? (Thursday or Friday release) Or do you want to keep this going right up until Tuesday's RC release?
I would prefer to keep it as late as possible, but I don't want to inconvenience people if it's a big hassle. I leave it to your discretion.
Comment on attachment 8906948 [details] [diff] [review] patch for 56 This needs to go on m-r before 56.0-build1.
Status: NEW → RESOLVED
Last Resolved: 11 months ago
status-firefox56: affected → fixed
status-firefox57: --- → wontfix
Resolution: --- → FIXED
Managed to verify this issue on Firefox 56.0, under Windows 10x64, Ubuntu 16.04x86 and under macOS 10.12. Currently TLS 1.2 is set by default on the build under test.
Status: RESOLVED → VERIFIED
status-firefox56: fixed → verified
You need to log in before you can comment on or make changes to this bug.