On 8/23/21 3:04 AM, Kai Engert wrote:
Bob,
FYI, the usual deadline for the NSS version of ESR is 4 weeks prior to
the release of a new ESR, which is the time ESR goes into beta.
The agreement we've had is that is 2 release prior. The biggest issue is
a major change like this was not announced on this list and all the
stake holders were not brought in.
But that is currently water under the bridge. I'm in a real pickle
because of this, and I'm just looking for approval to ship our ESR with
the old NSS. At this point it's really can I ship it with the old NSS,
or do I have to wait 8 months to ship ESR. I really don't have any other
choice (our FIPS plan is such that I can no longer change NSS version
until 2022).
My proposed plan going forward is to pick up NSPR 4.32, leave NSS 3.67
(patch our ESR to accept 3.69) and backport any security patches to NSS
3.68.x into our NSS 3.67 and resync at the next ESR.
What I need is is this an acceptible plan for mozilla, or will we be in
trouble for this.
bob
Kai
--
You received this message because you are subscribed to the Google Groups
"dev-tech-crypto@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to dev-tech-crypto+unsubscr...@mozilla.org.
To view this discussion on the web visit
https://groups.google.com/a/mozilla.org/d/msgid/dev-tech-crypto/7854a2f4-f735-cb4b-0285-f95a81c43248%40redhat.com.
