> Hmmm ... its not clear what exploit is used (from just reading the file at
> the URL you gave).
I think "DIZZYTACHOMETER" doesn't exploit anything itself, but is just hiding
e.g. a rootkit installation by manipulating the rpmdb based on already existing
write permissions gained before. I didn't find the binary nor any source for
"DIZZYTACHOMETER", but the way of usage makes me assuming "regular" rpmdb
manipulations, not a RPM related security flaw.
> The provision in RPM for careful rootkit forensics is to use "rpm -Vp ..."
> from a CDROM (or other offline/immutable media).
Immutable media…something that is harder and harder to get when looking to
Fedora or RHEL (last with CDN). Sometimes (e.g. at EPEL as 3rd party
repository) the RPM package has been already orphaned and thus removed from the
repository when it comes to a verification case.
> This isn't an easy problem to solve.
Right, and I don't expect a quick solution. Just wild ideas: Blockchains for
rpmdb? Optionally trusted (digital) timestamping for rpmdb? But yes, maybe also
a further verification tool that somehow handles the situation that offline
media is going away. I do not have a specific idea how this could be solved,
finally.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/196#issuecomment-292949590
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
