Re: NSS 3.69 Release

Robert Relyea <[email protected]> Mon, 23 Aug 2021 16:48:14 -0700
Newsgroups gmane.comp.mozilla.crypto
Message-ID <[email protected]>
On 8/23/21 4:21 PM, Martin Thomson wrote:
> |Bug 1717610 <https://bugzilla.mozilla.org/show_bug.cgi?id=1717610>| 
> is a risk here; it might be that the ESR code depends on that function 
> being present.  But if you want to backport it, I don't see a problem.

Actually that's not an issue because we don't ship that code in our NSS 
release since it's never been integrated into the NSS builds;). Our 
Firefox team must have their own copy.

At some point we should make it a issue.... I'd really love to loose 
libpkix;).


bob

>
> On Tue, Aug 24, 2021 at 1:45 AM Robert Relyea <[email protected] 
> <mailto:[email protected]>> wrote:
>
>     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 "[email protected]
>     <mailto:[email protected]>" group.
>     To unsubscribe from this group and stop receiving emails from it,
>     send an email to [email protected]
>     <mailto:dev-tech-crypto%[email protected]>.
>     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
>     <https://groups.google.com/a/mozilla.org/d/msgid/dev-tech-crypto/7854a2f4-f735-cb4b-0285-f95a81c43248%40redhat.com>.
>

-- 
You received this message because you are subscribed to the Google Groups "[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-tech-crypto/209196e6-7e3e-0687-15c2-3fdf07269a9b%40redhat.com.