Please help: how to relocate installed files paths into an RPM database

Greg_Swift at Greg_Swift at
Wed Aug 12 13:09:54 UTC 2009

> I tried your suggestion and it works, however, since it implies
> reinstalling all the packages from their RPM files, though in
> database only, is no so different from reinstalling them completely.
> If no standard solution is available, I was looking for a sort of
> hack such as a query to manipulate the database directly. I guess
> RPM development team should take this in consideration because it
> allows a better portability of every RPM-based installation.

Well, depending on any changes you've made and how big the install base is,
it can be a lot smaller and quicker to perform.  I think some would argue
that having an easy direct way of manipulating the database would defeat
some of the purpose of the security the RPM database helps provide.

Take for instance this scenario:

A hacker gets on my box and does a relocate of an important package (like
procps) to a directory outside of everyone's path, and then drop installs a
custom rpm with a name like procps- that provides similar files, but with
malicious content.  A rpm -qaV show the files all validating fine, and a
rpm -q --whatprovides shows something that looks right... it isn't a pretty

Although... i'm not sure if procps is relocatable.  But i think the point
still stands.

anyone else?


More information about the Rpm-list mailing list