Re:Snyk security researcher deploys malicious NPM packages t...
by __MatrixMan__ on Tuesday January 14, 2025 @07:24PM
(#42705840)
As far as I'm aware it's missing the consensus part. If I run a program that's not supposed to touch the filesystem in any way, and it does, SELinux doesn't suggest a way for me to circulate this new knowledge among other users of this program--except through its maintainer or that of my Linux distro. And maintainer diligence is over-relied-on as it is.
Ideally this sort of thing would work just as well on bits for which there was no clear maintainer. Like if SETI turned up a signal which we can chmod +x and run, we could use such a thing to crowd source an understanding of what it does.
A way to hash a file and ask:
> What is known about these bits?
If it's a popular program and yet none of your peers have seen that hash, maybe you should subject it to more scrutiny than if there's widespread consensus about it.
Ideally this sort of thing would work just as well on bits for which there was no clear maintainer. Like if SETI turned up a signal which we can chmod +x and run, we could use such a thing to crowd source an understanding of what it does.
A way to hash a file and ask:
> What is known about these bits?
If it's a popular program and yet none of your peers have seen that hash, maybe you should subject it to more scrutiny than if there's widespread consensus about it.