News for hackers. Stuff that matters.
Re:Vagrant 2.0 by thrownhwn on Thursday September 07, 2017 @03:12PM (#15194850)
Anybody know if they has code-signed their Windows and macOS binaries with 2.0?

It's a shame so many "core" developer tools are not code-signed. It makes life hard in companies where binary whitelisting is used.

Re:Vagrant 2.0 by korzun on Thursday September 07, 2017 @04:08PM (#15195240)
> It makes life hard in companies where binary whitelisting is used.

The application would still have to be audited, signed or not, prior to whitelisting.

Re:Vagrant 2.0 by sslalready on Thursday September 07, 2017 @05:16PM (#15195800)
In practise it's much easier to just trust well-known developers by whitelisting their code-signing certificates.

You could still get owned, of course, but the benefit here is that you're excluding everything not explicitly whitelisted, including drive-by downloads, crap on portable devices or random programs downloaded off the internet that someone thinks will solve their problem of the day.

When people do not code-sign their software every software update is painful. At work, where we run https://github.com/google/santa, it frequently happens that companies with code-signed software forget to code-sign their auto-updater, or random binaries that run during installation. Most of the time the application crashes/hang during the update (because some piece weren't allowed to run), only to remind to you update the software again when you restart the application.

Re:Vagrant 2.0 by aoeuasdf1 on Thursday September 07, 2017 @06:03PM (#15196183)
Does santa work with brew? If not, how do you even function?
Re:Vagrant 2.0 by sslalready on Thursday September 07, 2017 @08:29PM (#15197032)
Personally I've managaged to avoid using it so far. But yes, you can whitelist individual binaries or even directories. The lack of code-signing doesn't prevent whitelisting, it just makes your life harder than necessary.
Re:Vagrant 2.0 by trapperkeeper74 on Thursday September 07, 2017 @03:36PM (#15195022)
It also creates an unnecessary attack surface against core infrastructure.