Hacker News Reader

Thankfully it's rather trivial to do.

It's trivial to do when you know which binary to replace (and you have the source code available).

But it's probably not so trivial to hunt down every single old binary on every system. There's also a continuous risk that you may receive old binaries from third parties in the future.

For example, gitlab has started to ship a component written in Go in recent versions. Things like these are easy to forget about.

If you can't track the binaries you are running you have a bigger problem than recompiling some of them. Security issues aren't the one in a decade thing, if you can't easily locate which code has to be updated, you are in trouble already...

I'd say as a general overzealous rule that if at least two people in the company don't know the code, it shouldn't be publicly accessible if it being compromised could cause you financial harm.

Reply on news.ycombinator.com