Closed Bug 741135 Opened 10 years ago Closed 10 years ago
Update Mozilla to NSS 3
I am preparing the NSS 3.13.4 release. The first CVS tag I will push to mozilla-central (via mozilla-inbound) is NSS_3_13_4_BETA1, which has the following bug fixes: Bug 577747: Memory leak in ECDSA code in secvfy.c Bug 640625: export to PKCS #12 does not iterate hashing Bug 644764: AES256 not recorded in SMIME capabilities Bug 647364: CERT_PKIXVerifyCert doesn't check cert->trust of the leaf certificate Bug 671069: signed/unsigned warnings in pk11wrap Bug 671071: const/non-const warnings in lib/certdb/stanpcertdb.c Bug 697420: crash in [@ CERT_DestroyOCSPResponse] Bug 715073: Insufficient length checking in QuickDER decoder Bug 723740: CKM_DH_DERIVE does not respect VALUE_LEN if VALUE_LEN is greater than the unpadded generated key. Bug 726134: Allow CERT_PKIXVerifyCert to return a NULL trust anchor cert (cert_po_trustAnchor) Bug 727691: SSL_InvalidateSession crashes if session cache was disabled Bug 728919: [patch] Fix clang warning in sslcon.c Bug 729377: SEC_RegisterDefaultHttpClient and CERT_RegisterAlternateOCSPAIAInfoCallBack should set the SEC_ERROR_NOT_INITIALIZED error if they are called before NSS is initialized Bug 729380: Declaring variables on the beginning of a line confuses cvs diff -p Bug 729721: Miscellaneous code cleanups in libpkix for NSS 3.13.4 Bug 732258: ssl3_FinishHandshake cleanup Bug 732630: Prefer SSL_RSA_WITH_RC4_128_SHA over SSL_RSA_WITH_RC4_128_MD5 Bug 734534: Fix a buffer length bug and nits in the next protocol negotiation (NPN) functions Bug 737395: SECITEM_CompareItem() returns invalid result, found with memory analysis tool that uses its own copy of "memcmp" Bug 737802: regression: SSL step-up EKU OID no longer treated as SSL Server type Bug 738161: Fix "beause" spelling in /security/nss/lib/pk11wrap/pk11auth.c
Update NSS to NSS_3_13_4_BETA1. mozilla-inbound changeset URL: http://hg.mozilla.org/integration/mozilla-inbound/rev/9b278853a823
Priority: -- → P2
Whiteboard: [Leave open after merge]
Assuming we'll want to take this uplift on the ESR branch eventually, maybe for the Firefox-13-equivalent release in June?
Assignee: wtc → kaie
This attachment is a placeholder for branch approvals for upgrading to NSS 3.13.4 in the Mozilla tree. It's currently too close to the April 24 releases to take this on the beta or ESR branches. We should land on mozilla-central, and if that looks good land on Aurora. Make sure we land on Aurora before April 24 and this will be automatically set for shipping with Firefox 13 in June. Sometime after April 24--when we've had sufficient beta feedback on the changes--we can land this on the ESR branch. Since we've pushed the MD5 changes out to 3.13.5 we're not expecting any compatibility problems, but better safe than sorry.
Attachment #612691 - Attachment is obsolete: true
Comment on attachment 612692 [details] [diff] [review] approval placeholder Requesting approval for aurora
Attachment #612692 - Flags: approval-mozilla-aurora?
Comment on attachment 612692 [details] [diff] [review] approval placeholder Requesting approval for ESR 10.0.5
Attachment #612692 - Flags: approval-mozilla-esr10?
Update NSS to NSS_3_13_4_BETA2. mozilla-inbound changeset URL: https://hg.mozilla.org/integration/mozilla-inbound/rev/f6cb35021951
Comment on attachment 612692 [details] [diff] [review] approval placeholder [Triage Comment] Approving for Aurora 13, and holding on approving for the ESR until after the version bump on that branch.
Attachment #612692 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Summary: Update NSS to NSS 3.13.4 in mozilla-central → Update Mozilla to NSS 3.13.4
Landed RTM versions into inbound. https://hg.mozilla.org/integration/mozilla-inbound/rev/11b6ea48df17 The bug can be marked fixed after this commit was merged into mozilla-central.
Whiteboard: [Leave open after merge]
Aurora for Fx13: https://hg.mozilla.org/releases/mozilla-aurora/rev/beef2cc3afb0
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla14
Attachment #612692 - Flags: approval-mozilla-esr10? → approval-mozilla-esr10+
@wtc, can you please verify this is fixed with Firefox 13 and latest-mozilla-esr10?
Anthony: I'm sorry I forgot to reply. I remember I verified this was fixed in Firefox, but I didn't know how to verify it in latest-mozilla-esr10.
How did you verify it in Firefox? I assume ESR would be no different.
I must have verified it in Firefox 13 by inspecting the source file security/nss/TAG-INFO in the Hg repository for Firefox 13. I may have also installed a Firefox 13 build. I don't know the Hg repository for latest-mozilla-esr10.
http://hg.mozilla.org/releases/mozilla-esr10/file/tip/security/nss/TAG-INFO states "NSS_3_13_5_RTM". I suppose we can call this bug verified then.
You need to log in before you can comment on or make changes to this bug.