[Rpm-maint] [rpm-software-management/rpm] RPM's user/group cache isn't flushed across chroot (Issue #4093)

[Panu Matilainen]

pmatilai created an issue (rpm-software-management/rpm#4093)

RPM cache's some user and group information in a global cache known as `rpmug`, regardless of where and when the information was looked up, with no regards to operating on the system itself or (possibly multiple) chroot paths, among which user/group details can of course differ.

This "works" for rpm(8) in the sense that rpm itself only looks up user/group info on one side of a chroot and there can only be a single chroot in a process lifetime. But that doesn't necessarily hold for other kinds of clients and API users - if a client does multiple transactions to different chroots within a single process lifetime, it *will* get user/group information wrong sooner or later.

`rpmug` needs to track the chroot path it's currently caching, and flush whenever that changes (including going in and out of a chroot)

This bug is no less than 29 years old 😄 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/4093
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/issues/4093 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20260121/e12b17e7/attachment.htm>