Closed
Bug 915930
(mozilla::pkix)
Opened 11 years ago
Closed 11 years ago
Make mozilla::pkix the default certificate verifier
Categories
(Core :: Security: PSM, defect, P2)
Core
Security: PSM
Tracking
()
RESOLVED
FIXED
mozilla31
People
(Reporter: briansmith, Assigned: cviecco)
References
(Blocks 2 open bugs)
Details
(Keywords: feature)
Attachments
(1 file, 1 obsolete file)
2.48 KB,
patch
|
briansmith
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Reporter | ||
Updated•11 years ago
|
Alias: insanity::pkix
Reporter | ||
Updated•11 years ago
|
Assignee: nobody → brian
Status: NEW → ASSIGNED
Reporter | ||
Comment 1•11 years ago
|
||
Matt, I'd like us to run the same kind of tests that we ran for testing TLS 1.2 compatibility against this feature, using the scripts you wrote. I suspect that we'll be ready for doing that testing in a day or two. If at all possible, we should try to do the compatibility testing in the next couple of weeks, if not sooner. If that time frame doesn't work for you, could you please send me the latest version of your testing script so I can try to run it? This is a high-priority feature and parts of it were uplifted to Firefox 29 already.
Flags: needinfo?(mwobensmith)
Keywords: qawanted
Comment 2•11 years ago
|
||
Sounds great. Will do. We can run the script at any time.
Just let me know when we are ready to do so, as it sounds as if there are dependencies that we are waiting on.
Flags: needinfo?(mwobensmith)
Updated•11 years ago
|
QA Contact: mwobensmith
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Updated•11 years ago
|
Blocks: mozilla::pkix-beta
Reporter | ||
Updated•11 years ago
|
Priority: -- → P2
Reporter | ||
Comment 3•11 years ago
|
||
This should go in the Firefox 30 release notes.
This should not go into the Firefox 29 release notes.
I suspect you may want to wait until it is RESOLVED FIXED though.
relnote-firefox:
--- → ?
Comment 4•11 years ago
|
||
Re-assigning the tracking bug because I'm basically on the hook for this.
Assignee: brian → dkeeler
Reporter | ||
Updated•11 years ago
|
Assignee: dkeeler → brian
Reporter | ||
Updated•11 years ago
|
Comment 5•11 years ago
|
||
I'm beginning the renaming of open bugs with "insanity::pkix" in the title as part of renaming the project to "mozilla::pkix". You'll likely receive a lot of bugspam. Apologies in advance.
Alias: insanity::pkix → mozilla::pkix
Summary: Make insanity::pkix the default certificate verifier → Make mozilla::pkix the default certificate verifier
Comment 6•11 years ago
|
||
Since bug 986156 is inbound and bug 987295 and bug 989516 are ready to land, we're looking to turn this on today. The intention of this patch is to add the pref (default false) to anything using gecko. Adding the pref (default true) in firefox.js makes it so it is only enabled in Firefox.
Attachment #8399611 -
Flags: review?(cviecco)
Attachment #8399611 -
Flags: feedback?(brian)
Assignee | ||
Comment 7•11 years ago
|
||
Comment on attachment 8399611 [details] [diff] [review]
patch
Review of attachment 8399611 [details] [diff] [review]:
-----------------------------------------------------------------
Why dont we make another bug (with this patch) to enable mozilla::pkix in firefox(only) and leave this when we what to have all products with it as default? (when we actually change the value in nsNSSComponent)
Attachment #8399611 -
Flags: review?(cviecco) → review-
Comment 8•11 years ago
|
||
Attachment #8399611 -
Attachment is obsolete: true
Attachment #8399611 -
Flags: feedback?(brian)
Updated•11 years ago
|
Target Milestone: --- → mozilla30
Comment 9•11 years ago
|
||
Do we know if it is going to be shipped with 30?
Assignee | ||
Comment 10•11 years ago
|
||
It is on 30,(In reply to Sylvestre Ledru [:sylvestre] from comment #9)
> Do we know if it is going to be shipped with 30?
The new certverifier is on 30 but it is not enabled by default as it has several performance and compatibility issues. The goal is default for 31.
Assignee | ||
Updated•11 years ago
|
Assignee | ||
Comment 11•11 years ago
|
||
Assignee | ||
Comment 12•11 years ago
|
||
Hey brian, can you take a look at the patch. Do you think we can land this as default before 31 becomes aurora? (if so please review the patch) I can land it.
Flags: needinfo?(brian)
Assignee | ||
Comment 13•11 years ago
|
||
Comment on attachment 8412359 [details] [diff] [review]
make-mozilla-pkix-default-certverifier
Review of attachment 8412359 [details] [diff] [review]:
-----------------------------------------------------------------
This fill fix an issue on android (Bug 1001240) so we want it before the uplift on monday (this is just flippling a switch for all gecko instead of only for desktop).
Attachment #8412359 -
Flags: review?(honzab.moz)
Reporter | ||
Updated•11 years ago
|
Assignee: brian → cviecco
Flags: needinfo?(brian)
Reporter | ||
Comment 14•11 years ago
|
||
Comment on attachment 8412359 [details] [diff] [review]
make-mozilla-pkix-default-certverifier
Review of attachment 8412359 [details] [diff] [review]:
-----------------------------------------------------------------
Thanks. I suggest emailing dev-platform to let the Thunderbird/SeaMonkey people know that they should look for trouble. You may want to explicitly mention bug 982340 to them.
Attachment #8412359 -
Flags: review?(honzab.moz) → review+
Reporter | ||
Updated•11 years ago
|
Assignee | ||
Comment 15•11 years ago
|
||
Comment 16•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 17•11 years ago
|
||
Marking tracking for 31 so that we can get this into QA test plans while it's on beta -- can someone put in steps for QA verification on this new feature?
status-firefox30:
--- → fixed
status-firefox31:
--- → fixed
tracking-firefox31:
--- → +
Flags: needinfo?(twalker)
Flags: needinfo?(cviecco)
Flags: needinfo?(anthony.s.hughes)
Comment 18•11 years ago
|
||
This page should have the information necessary to test: https://wiki.mozilla.org/SecurityEngineering/mozpkix-testing#Request_for_Testing
Testing basically consists of browsing https sites and making sure we get the same results as before (in some cases the behavior is different, but we definitely shouldn't be breaking any sites that use a certificate signed by a CA in our root program). The pref "security.use_mozillapkix_verification" controls whether or not the new library is in use.
There's also an automated compatibility testing script Matt Wobensmith developed. It would be great to run that, too.
Flags: needinfo?(cviecco)
Comment 19•11 years ago
|
||
(In reply to Lukas Blakk [:lsblakk] from comment #17)
> Marking tracking for 31 so that we can get this into QA test plans while it's on beta
Assuming you mean Firefox 30 Beta based on the status flags. Matt is already assigned here so I trust he can take care of verifying this is fixed.
Comment 20•11 years ago
|
||
Yes, I'll own QA verification. Thanks all.
Comment 21•11 years ago
|
||
This doesn't look to have landed on 30 at all - can someone confirm? I see it landing pre-merge to central (31). Also, yes, Matt will have this (my confusion was about this not being a sec bug)
tracking-firefox30:
--- → +
Comment 22•11 years ago
|
||
This feature was targeted for Fx31. I believe it's present in Fx30 but off by default.
Comment 23•11 years ago
|
||
Added in the release notes: "mozilla::pkix as default certificate verifier"
Comment 24•11 years ago
|
||
This isn't meant to be enabled in 30.
status-firefox30:
affected → ---
tracking-firefox30:
+ → ---
Updated•11 years ago
|
Target Milestone: mozilla30 → mozilla31
Comment 25•10 years ago
|
||
Hi Matt, as we get close to the release for 31 we're looking to verify all fixes marked as "verifyme". Since this is one of them, I wanted to ask you whether you're handling this one or if you need some help from us.
Flags: needinfo?(mwobensmith)
Comment 26•10 years ago
|
||
The default setting for mozilla::pkix in Fx31 is indeed turned on, so I am marking this as verified.
Keywords: verifyme
Updated•10 years ago
|
Flags: needinfo?(mwobensmith)
Reporter | ||
Updated•10 years ago
|
Depends on: CVE-2014-8642
You need to log in
before you can comment on or make changes to this bug.
Description
•