News for hackers. Stuff that matters.
Re:Go 1.5.3 released to address security vulnerability by tptacek on Wednesday January 13, 2016 @08:22PM (#10898996)
This is a problem with relying on APT for security fixes anyways.

It's been particularly bad in the past for things like nginx, where we've known about memory corruption bugs for multiple days and had clients who were incapable of patching because they only had infrastructure for downloading packages.

You should have tools in place to build, from source, anything that might be a significant security issue.

Re:Go 1.5.3 released to address security vulnerability by eropple on Thursday January 14, 2016 @02:24AM (#10900056)
If my clients would pay me for it, I certainly would. But `package 'foo'` is a lot cheaper than that, turns out.

And while I 100% agree about the optimal case, in practical terms you're going to see a lot better turnaround from the maintainers of Debian's OpenSSL than, say, the third-party Docker repo. A sane system not reliant on static linking 'til the cows come home is not a cure-all, but it's better than the Go situation, and is a part of why I'm super not thrilled with Go-as-infrastructure. (Go-as-app, whatever, people take that problem on themselves.)

Re:Go 1.5.3 released to address security vulnerability by xorcist on Thursday January 14, 2016 @05:31AM (#10900529)
The problem isn't really with APT (or deb). Building a package from source is trivial. Anyone can do it, and it's completely automated. Building software from upstream source can be a lot more daunting.