[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Wheezy update of nss?


That decision is taken on a case-by-case basis. The reason it was
synchronized last time was due to

We had to update nspr to a new version and then it made sense to
update nss too. That caused a clear regression in chromium (formally
not supported) so it may had been better to keep nss as before and
just fix the call to the new function in nspr.

I'd say that it is less likely to cause a new regression this time as
the jump is much smaller.

I'd say you have to judge yourself.

I do not think it matters much whether you upgrade wheezy or jessie
first. You can even upgrade both if you like. :-)

// Ola

On 29 November 2016 at 21:49, Antoine Beaupré <anarcat@orangeseeds.org> wrote:
> What is the situation with nss now? I see that 3.26 seems to be in all
> suites now - do we make coordinated releases across all suites?
> This is fixed by the 3.26.2 update but I am hesitant in upgrading wheezy
> to 3.26.2 before jessie...
> See https://security-tracker.debian.org/tracker/CVE-2016-9074
> a.
> --
> Only in the darkness can you see the stars.
>                         - Martin Luther King, Jr.

 --- Inguza Technology AB --- MSc in Information Technology ----
/  ola@inguza.com                    Folkebogatan 26            \
|  opal@debian.org                   654 68 KARLSTAD            |
|  http://inguza.com/                Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /

Reply to: