We want to create a combined release based on NSS 3.12.4 plus several new CA root certificates into Mozilla.
Hi, not beeing included in the current Beta4 of FireFox either...I take the liberty to submit a "request for status" for this bug.
If this is wanted for Firefox 3.6 it may already be too late, and certainly needs to be on the release radar if it's going to make it.
This doesn't block the release, but if it can land in the next 24 hours, it can have my approval to land. I can't set an approval flag without a bug, but a check-in that:
- adds the new roots
- doesn't otherwise signifcantly alter NSS behaviour/functionality (i.e. doesn't introduce additional code risk)
No patch for this bug.
The instructions are:
"Follow the usual procedure from https://developer.mozilla.org/en/Updating_NSPR_or_NSS_in_mozilla-central to update Mozilla to NSS tag NSS_3_12_4_WITH_CKBI_1_77_RTM."
I've verified the difference between "nss currently being used" and "new nss tag NSS_3_12_4_WITH_CKBI_1_77_RTM" is equivalent to the root additions made with nss bug 527759.
In today's NSS meeting, Bob Relyea, Nelson Bolyard and Dan Veditz have agreed to the plan to deliver the changes from bug 527759 tag to Mozilla, which I take as r+
pushed to mozilla-central
pushed to mozilla-1.9.2
Kai - are you able to land this and bug 527759 on 1.9.1 in the next day or so? We're behind on getting 188.8.131.52 out the door, so if you can't get to it, I can try.
(In reply to comment #7)
> Kai - are you able to land this and bug 527759 on 1.9.1 in the next day or so?
> We're behind on getting 184.108.40.206 out the door, so if you can't get to it, I can
by which I mean that we're behind on getting 220.127.116.11 out the door. 18.104.22.168 should be about a year away.