The default bug view has changed. See this FAQ.

NSS_3_11_10_WITH_CKBI_1_67_RTM for 1.8 branch

RESOLVED FIXED

Status

()

Core
Security: PSM
RESOLVED FIXED
8 years ago
8 years ago

People

(Reporter: Alexander Sack, Assigned: Alexander Sack)

Tracking

({fixed1.8.1.21})

unspecified
x86
Linux
fixed1.8.1.21
Points:
---
Dependency tree / graph
Bug Flags:
blocking1.8.1.next +
wanted1.8.1.x +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

600 bytes, patch
Samuel Sidler (old account; do not CC)
: review+
Samuel Sidler (old account; do not CC)
: approval1.8.1.next+
Details | Diff | Splinter Review
(Assignee)

Description

8 years ago
1.8 branch wants to pick up the NSS fix for bug 471715.

NSS_3_11_10_WITH_CKBI_1_67_RTM is what we might want for that.

Note that current NSS on 1.8 branch is NSS_3_11_9_RTM.
(Assignee)

Comment 1

8 years ago
Created attachment 359745 [details] [diff] [review]
update client.mk NSS tag

currently using ffox 2 with the updated NSS .. seems to work for the use cases tested so far.
(Assignee)

Comment 2

8 years ago
Samuel, what testing do you think is needed besides some insight on the changes done from 3.11.9 and .10 before we could consider to land this on branch?
Really, I'd just like a list of changes and for someone from the NSS tag to comment on the testing that's already been done.

Upping NSS on the 1.8.1 branch means our QA team needs to do some extra testing after it lands to ensure that it doesn't break anything in Thunderbird (since that's all MoCo is still shipping). Normally, things have been caught when testing Firefox, but since we aren't doing that anymore, I'm afraid we might miss something. If you (or any of the Linux distros) are putting it in your release, that might be enough testing, but Al should comment here. Al?
Flags: wanted1.8.1.x+
Flags: blocking1.8.1.next?
I don't have enough of a history with NSS to know what problems it has caused in the past or how it interacts with Thunderbird. My fear would be that it would destabilize Thunderbird (and potentially work by others in 1.8.1). What are the real risks with this change? What has happened when we've changed this before?
(Assignee)

Comment 5

8 years ago
ok, seems like this has to wait for 1.8.1.22 as this needs some documentation (NSS changes) baking and QA for tbird and other 1.8 apps.
Blocking, but we do need to know what the diff is between 3.11.9 and 3.11.10 so it can be verified
Flags: blocking1.8.1.next? → blocking1.8.1.next+
Duplicate of this bug: 478316

Comment 8

8 years ago
I don't have a list of high level changes between 3.11.9 and 3.11.10 and I'm afraid other people might not have either.

The 3.11.x branch is a highly stable branch that only receives handpicked bug fixes. It received the usual NSS testing of automated testsuite runs.

This update is also required in order to fix bug 478755.

Updated

8 years ago
Blocks: 478755

Comment 9

8 years ago
On the 3.11.9 release page I found the approximate release date.
Here is a bonsai query that lists all the changes to NSS in cvs after that date:

http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=NSS_3_11_BRANCH&branchtype=match&dir=mozilla%2Fsecurity%2Fnss+mozilla%2Fsecurity%2Fcoreconf+mozilla%2Fsecurity%2Fdbm+mozilla%2Fdbm&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2008-01-31&maxdate=&cvsroot=%2Fcvsroot
Comment on attachment 359745 [details] [diff] [review]
update client.mk NSS tag

I looked through the changes and feel more comfortable with approving this.

Alexander: Can you make sure this gets landed by Friday?
Attachment #359745 - Flags: review+
Attachment #359745 - Flags: approval1.8.1.next+
I'm giving this to Alexander since he made the patch in this bug and ultimately needs to land it.
Assignee: kaie → asac
Fix checked in on the 1.8 branch
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Keywords: fixed1.8.1.21
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.