News for hackers. Stuff that matters.
Re:Log4j: The pain just keeps going by shepherdjerred on Wednesday July 20, 2022 @01:03PM (#32168771)
> So the exact software you compile will depend on whether or not you can connect to a 3d party service? Do you understand the actual implications of this?

This is already true with the vast majority of software using any an online software repository, e.g. Go, NodeJS, Java, Rust, etc.

Re:Log4j: The pain just keeps going by laughingbovine on Wednesday July 20, 2022 @01:25PM (#32169147)
Yeah but you can cache the packages or store them in some fashion. I've seen JAR files in git repos far too many times...

With security, you need some online service so you can find the new CVEs every day.

Re:Log4j: The pain just keeps going by kelnos on Wednesday July 20, 2022 @04:38PM (#32171971)
> With security, you need some online service so you can find the new CVEs every day.

Or you just do it manually if that service is down. It's weird to me that the argument for not having an automated, 3rd-party service is "if it goes down then you'll have to do things manually", when the alternative is "you always have to do it manually".

If you are comfortable trusting a third-party service to tell you when to upgrade, then that is absolutely an improvement over doing security updates manually. This is why I have unattended-upgrades set up on my Debian systems to automatically install updates from Debian Security every day. Sure, it may fail for whatever reason, but I am certainly not going to take the time to (or even remember to) update every day.

Re:Log4j: The pain just keeps going by staticassertion on Wednesday July 20, 2022 @05:33PM (#32172669)
Yeah, honestly there's probably just a few libraries you're going to have to care about re: keeping up to date. Everything else can get updated opportunistically/ on some cadence. Your exposed attack surface for most software is pretty much your TLS library and network stack. The more mature you become the more of the attack surface you can try to track.

But basically if you just subscribe to a few projects' releases you can pretty easily get things pushed to you when it matters.

Re:Log4j: The pain just keeps going by shepherdjerred on Wednesday July 20, 2022 @10:13PM (#32175004)
Oh I completely agree. I was referring to the parent saying that a third party is dictating what to build -- for security this is inevitable. For dependencies this can be solved by caching your .jars or whatever, but at some point you still always have a third party dictating what you're building.
Re:Log4j: The pain just keeps going by philosopher1234 on Wednesday July 20, 2022 @01:05PM (#32168798)
Not Go
Re:Log4j: The pain just keeps going by mrcarruthers on Wednesday July 20, 2022 @01:10PM (#32168886)
Still Go. I mean there's no central repository in the way there's one for npm, and yes you can point it to any git repo as the source for your dependencies, but the reality is most are on GitHub. So your central repository is GitHub.
Re:Log4j: The pain just keeps going by shepherdjerred on Wednesday July 20, 2022 @10:08PM (#32174963)
Can you give me an example of a popular Go project that doesn't have any dependency on GitHub?