News for hackers. Stuff that matters.
Re:SolarWinds: What Hit Us Could Hit Others by SahAssar on Tuesday January 12, 2021 @05:29PM (#25754852)
> You can reduce the benefit of such a hack by not having information critical enterprises all running the same binary blob.

That assumes that you actually inspect the source, right?

Re:SolarWinds: What Hit Us Could Hit Others by joe_the_user on Tuesday January 12, 2021 @05:48PM (#25755078)
If Solarwinds was distributed as source to hundreds of companies, maybe many would not bother diffing the source from the previous version but it seems plausible that a few would look at these at the least, especially given you are talking corporations who follow deployment procedures.

The build process itself could spit out the diffs at the end, for example.

Re:SolarWinds: What Hit Us Could Hit Others by Pokepokalypse on Tuesday January 12, 2021 @07:24PM (#25756161)
well, you still have a 'tragedy of the commons' situation if say 10,000 users are all counting on at least 1 user to inspect the source - but with no commercial incentive to do so, nobody does.

How does a user of open source ever know or measure exactly how well the source code has been scrutinized?

Re:SolarWinds: What Hit Us Could Hit Others by joe_the_user on Tuesday January 12, 2021 @09:50PM (#25757397)
I'm getting this "open source doesn't guaranteed there's no problem" claim. And I'd agree open source doesn't guarantee there's no problem. But it seems clear that routes which have allowed malware to be pushed automatically are fundamental, guarantee problems and malware in source code is a potential problem with an obvious answer.