3 ms·
That's precisely what it's supposed to do. If you update the Tripwire db every time you "initiate an action that causes monitored files to change" - then it doe
by bigiain 10y ago
That's precisely what it's supposed to do. If you update the Tripwire db every time you "initiate an action that causes monitored files to change" - then it does a _magnificent_ job of telling you when someone _else_ changes those files.
You need to run 'tripwire --update' every time you run 'apt-get update' or 'pip install foo' or 'npm install bah' or whatever - then you wont get that storm of false positives.
- mcbain 10y agoHonest question from an interested party: have you actually had it alert you about someone else changing the files? I've been in the previous boat: of having it running on a system I've inherited, and given up because it seemed too much hassle.
- bigiain 10y agoYes - a few times a year when normal and authorised things or people have unexpectedly changed files in tripwire-protected places, and in ~20 years I think three times when I'd had an intrusion. Those three timely notifications of real breaches have made 20+ years worth of occasional false positives 100% worth it.