- cross-posted to:
- hackernews@lemmy.smeargle.fans
- hackernews@derp.foo
- cross-posted to:
- hackernews@lemmy.smeargle.fans
- hackernews@derp.foo
Stealthy Linux rootkit found in the wild after going undetected for 2 years::Krasue infects telecom firms in Thailand using techniques for staying under the radar.
Honestly, is there much code in the world which doesn’t meet this description? How do you propose we decide what is trustworthy? Every time I update my packages I’m getting possibly millions of new lines of code that I can’t possibly personally vet
Keyword “Random”. The code for the packages that shipped for your os and for your user installed utilities are generally ‘trusted’ code since you sought out the install. It’s not bulletproof, but it’s a good start vs running any package that happens to land in your downloads folder.
Well, it’s not always so cut and dried. For example, do I need to research the maker of an app that looks useful? I don’t think most people on lemmy are the types to literally not care at all where software comes from, so I’m just trying to understand better how we can properly draw that line
Those packages are vetted by multiple maintainers from different places, they’d all have to be in on it.