News for hackers. Stuff that matters.
Re:Distribution packages considered insecure by koja86 on Monday February 22, 2016 @04:40AM (#11149652)
By using relase designation instead of toy codenames ("testing" instead of "Stretch") in apt config files I get pretty close to rolling realease. Using that and apt-pinning I am totally happy running stable/testing/unstable/experimental system with majority of packages from testing on my desktop. I am rather conservative and would avoid anything bleeding-edge on production systems so using stable with security updates (and stable-backports if needed) would be my choice. YMMV though.
Re:Distribution packages considered insecure by ckuehl on Monday February 22, 2016 @04:53AM (#11149717)
Just want to emphasize (and this is not directed specifically at you): you almost certainly shouldn't run Debian testing on anything that is public-facing. Packages get migrated to testing after some days in unstable if no high-priority bugs are filed against them during the days after their upload.

If a security patch is uploaded to unstable today, you won't get it in testing for a few days, and possibly many more if the migration gets blocked.

https://www.debian.org/devel/testing

Re:Distribution packages considered insecure by g1n016399 on Monday February 22, 2016 @04:59AM (#11149735)
You can install security updates from unstable using the output of debsecan:

apt-get -t unstable install $(debsecan --suite sid --format packages --only-fixed)

Re:Distribution packages considered insecure by ckuehl on Monday February 22, 2016 @05:05AM (#11149751)
Just keep in mind that unstable is not guaranteed to get security fixes promptly, either. The Debian Security Team only handles supported releases.

The Security Team FAQ is a good read: https://www.debian.org/security/faq#unstable

It's quite explicit in saying that if security is important to you, then you should run a supported release.