Closed
Bug 1320509
Opened 8 years ago
Closed 8 years ago
Firefox < 52.0 fails to build --with-system-nss where NSS >= 3.28
Categories
(NSS :: Libraries, defect)
Tracking
(firefox-esr45 unaffected, firefox50 wontfix, firefox51 wontfix, firefox52 unaffected, firefox53 unaffected)
RESOLVED
FIXED
3.28
Tracking | Status | |
---|---|---|
firefox-esr45 | --- | unaffected |
firefox50 | --- | wontfix |
firefox51 | --- | wontfix |
firefox52 | --- | unaffected |
firefox53 | --- | unaffected |
People
(Reporter: jbeich, Assigned: ekr)
References
Details
(Keywords: regression)
Attachments
(1 file)
1.99 KB,
patch
|
jbeich
:
feedback+
|
Details | Diff | Splinter Review |
API breakage makes it harder to check NSS itself for regressions.
$ echo ac_add_options --with-system-nss >>.mozconfig
[...]
In file included from obj-x86_64-unknown-freebsd12.0/security/manager/ssl/Unified_cpp_security_manager_ssl1.cpp:110:
security/manager/ssl/nsNSSCallbacks.cpp:1074:10: error: use of undeclared
identifier 'TLS_ECDHE_PSK_WITH_AES_128_GCM_SHA256'
case TLS_ECDHE_PSK_WITH_AES_128_GCM_SHA256: value = 70; break;
^
security/manager/ssl/nsNSSCallbacks.cpp:1075:10: error: use of undeclared
identifier 'TLS_ECDHE_PSK_WITH_CHACHA20_POLY1305_SHA256'
case TLS_ECDHE_PSK_WITH_CHACHA20_POLY1305_SHA256: value = 71; break;
^
security/manager/ssl/nsNSSCallbacks.cpp:1076:10: error: use of undeclared
identifier 'TLS_ECDHE_PSK_WITH_AES_256_GCM_SHA384'
case TLS_ECDHE_PSK_WITH_AES_256_GCM_SHA384: value = 72; break;
^
3 errors generated.
Assignee | ||
Comment 1•8 years ago
|
||
Assignee | ||
Comment 2•8 years ago
|
||
Thanks for the bug report. The attached patch to NSS should fix this.
I have removed the blocking flag as that bug is long-closed.
No longer blocks: 1304832
Comment on attachment 8814626 [details] [diff] [review]
0001-Bug-1320509-Restore-defines-for-PSK-cipher-suites.-r.patch
I confirm the patch is enough to unbreak --with-system-nss on Firefox 51 and 50.
Attachment #8814626 -
Flags: feedback+
(In reply to Eric Rescorla (:ekr) from comment #2)
> I have removed the blocking flag as that bug is long-closed.
Blocking regressing bug is a typical workflow for Core. The intent is to track fallout, so backporting a feature is more smooth. Does NSS do things differently?
Assignee | ||
Comment 5•8 years ago
|
||
Updated•8 years ago
|
Assignee: nobody → ekr
status-firefox50:
--- → affected
status-firefox51:
--- → affected
status-firefox52:
--- → unaffected
status-firefox53:
--- → unaffected
status-firefox-esr45:
--- → unaffected
Comment 7•8 years ago
|
||
(In reply to Jan Beich from comment #6)
> Can you backport the fix into NSS 3.28 ?
EKR, it seems this request makes sense, do you agree that we land the same patch into the 3.28 branch?
Flags: needinfo?(ekr)
Comment 8•8 years ago
|
||
Also asking Martin, so we potentially get "agreement for branch landing" more quickly.
Flags: needinfo?(martin.thomson)
Assignee | ||
Comment 9•8 years ago
|
||
Yes, I am fine with someone backporting this to 3.28
Flags: needinfo?(ekr)
Updated•8 years ago
|
Flags: needinfo?(martin.thomson)
Comment 10•8 years ago
|
||
Pushed to NSS_3_28_BRANCH for NSS 3.28
https://hg.mozilla.org/projects/nss/rev/36e8e898af98
I assume this can be marked fixed.
I'm not sure why this bug got tracking flags for Firefox. I think they aren't needed, because this problem is with NSS code, not with Firefox code.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: 3.29 → 3.28
Comment 11•8 years ago
|
||
Per comment #10, mark 51 won't fix.
Updated•7 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•