News for hackers. Stuff that matters.
Re:Debian 9 Stretch released by vbernat on Sunday June 18, 2017 @01:30PM (#14581777)
This is the case of many software. Usually, distribution support is longer than upstream. Therefore, distributors have to be backport the patches. That's what it is done for Debian.

They are few exceptions: any Oracle product (Oracle doesn't provide security patches and discourage people from making them) and Chromium (patches are too big) and Firefox (idem). For Chromium, the exception is to use the latest version. For Firefox, the exception is to switch to the next ESR once the current one becomes unmaintained.

Re:Debian 9 Stretch released by jancsika on Sunday June 18, 2017 @04:15PM (#14582652)
Thanks, I didn't realize that.

Do you know if these exceptions are documented somewhere deep in the Debian doc maze?

Re:Debian 9 Stretch released by jwilk on Monday June 19, 2017 @07:19AM (#14586041)
It's kinda documented in release notes:

https://www.debian.org/releases/stretch/amd64/release-notes/...

They don't mention the Oracle debacle, though.

Re:Debian 9 Stretch released by voltagex_ on Monday June 19, 2017 @08:41PM (#14591453)
>Unfortunately, this means that libv8-3.14, nodejs, and the associated node-* package ecosystem should not currently be used with untrusted content, such as unsanitized data from the Internet.

Jeez. I guess this means most people will be using other node binaries in production.

Re:Debian 9 Stretch released by vbernat on Sunday June 18, 2017 @04:59PM (#14582896)
If they are, I don't know where.