News for hackers. Stuff that matters.
Re:Why I Program in Go by tptacek on Sunday January 06, 2013 @12:20AM (#5015403)
Funny thing about Go is that as a compiled language, folks often need to send the source-code to the deployment servers to compile on them too. I seem to recall that deployment servers shouldn't need to have development tools which were themselves exposing the servers to bad intention by bad folks. It's just hard to keep the separation I guess.

This is what systems administrators with grey beards thought in the 1990s. A moment's thought about what an attacker who can run a compiler can do instead of running a compiler should be enough to inform you about how silly the idea is in practice.

Re:Why I Program in Go by jlouis on Sunday January 06, 2013 @07:29AM (#5016153)
It may have slowed down the occasional attacker who had no access to a HP-PA RISC cross compiler for his platform. But in todays world there is no reason.
Re:Why I Program in Go by meaty on Sunday January 06, 2013 @12:12PM (#5016821)
Well back in the 90s we kept the machines lean more because disk space was fucking expensive.
Re:Why I Program in Go by tptacek on Sunday January 06, 2013 @02:57PM (#5017487)
I'm not saying that minimal builds are silly, just that the idea of keeping compilers off systems as a security feature is.
Re:Why I Program in Go by wglb on Sunday January 06, 2013 @02:48PM (#5017456)
Did they have /bin/sh or /bin/bash or /bin/csh?
Re:Why I Program in Go by meaty on Sunday January 06, 2013 @04:01PM (#5017709)
Yes but they were only available to one user and that could only log in via the console server.

Joy to ACLs, custom Solaris builds and proper kit (ultra enterprise units the size of a full 42u rack).

I miss those days.