Closed Bug 1141394 Opened 6 years ago Closed 5 years ago

Remove the wreckage of SSLv3 support

Categories

(Core Graveyard :: Security: UI, defect)

defect
Not set
normal

Tracking

(firefox43 fixed)

RESOLVED FIXED
mozilla43
Tracking Status
firefox43 --- fixed

People

(Reporter: emk, Assigned: emk)

References

Details

Attachments

(1 file)

In bug 1106470, I intentionally left strings and idl constants in case we have to backout the change on beta or aurora.
Once the SSLv3 removal reaches to release, we can cleanup them.
Blocks: 1137991
Blocks: 1149581
No longer blocks: 1137991
With 39.0 having been released, is it time to proceed here, or wait a bit more for any regressions?
I'll wait at least until Chrome 44 is released.
(In reply to Masatoshi Kimura [:emk] from comment #2)
> I'll wait at least until Chrome 44 is released.

Chrome 44 was officially released on July 21 on the Google Chrome web site.
Assignee: nobody → VYV03354
Status: NEW → ASSIGNED
Attachment #8649827 - Flags: review?(dkeeler)
Comment on attachment 8649827 [details] [diff] [review]
Remove strings for SSLv3 warnings from the tree

Review of attachment 8649827 [details] [diff] [review]:
-----------------------------------------------------------------

r=me, but I think technically a browser/dom peer should sign off on this.
Attachment #8649827 - Flags: review?(dkeeler) → review+
Driveby r=me. Ship it!
Comment on attachment 8649827 [details] [diff] [review]
Remove strings for SSLv3 warnings from the tree

Victor, please review the devtools part.
Attachment #8649827 - Flags: review?(vporof)
Comment on attachment 8649827 [details] [diff] [review]
Remove strings for SSLv3 warnings from the tree

Oh, I missed comment #6.
Attachment #8649827 - Flags: review?(vporof)
https://hg.mozilla.org/mozilla-central/rev/52885a6f8ad6
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla43
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.