Please, please, clean up all the wrong entries. There should be a test which any package must pass before it can be rolled out.
The test should also include updates and corresponding scripts/triggers. It always drives me crazy when debsums -c is reporting something. Especially, I'm not sure if I can rely on virustotal to check detected files against malware (the virus scanners are somehow windows related).
In germany, we have a "federal trojan" created by our government which claims to also infect linux boxes. Not that I'm afraid of being a target. I'm rather afraid someone even worse than our government could reuse that malware (with some improvements, as our government has no idea about computing...).
As of today, debsums -c reports me
debsums -c x86_64- linux-gnu/ gbm/old. gbm_gallium_ drm.so x86_64- linux-gnu/ old.libgbm. so.1.0. 0
/usr/lib/
/usr/lib/
Please, please, clean up all the wrong entries. There should be a test which any package must pass before it can be rolled out.
The test should also include updates and corresponding scripts/triggers. It always drives me crazy when debsums -c is reporting something. Especially, I'm not sure if I can rely on virustotal to check detected files against malware (the virus scanners are somehow windows related).
In germany, we have a "federal trojan" created by our government which claims to also infect linux boxes. Not that I'm afraid of being a target. I'm rather afraid someone even worse than our government could reuse that malware (with some improvements, as our government has no idea about computing...).