Hello, On Nov 4 20:40 Andrei Borzenkov wrote (excerpt):
Johannes Meixner
writes: Is it possible to have an AppArmor profile for rpm so that rpm cannot change already existing files?
How would you update third party RPM with this profile active?
You cannot. This raises a subsequent issue: I assume it is too complicated (or simply impossible) to have an AppArmor profile for rpm so that rpm cannot change already existing files in other packages. Therefore "updating" third party RPMs with this profile active whould have to be done by first removing the installed third party RPM and then installing the new version of the third party RPM from scratch. I do not know how far this is feasible in practice. In particular it seems there is no rpm erase option like "--excludeconfigfiles" so that one could keep the RPM configfiles after package removal. In contrast all user-specific data is under /home/* where it is safe because /home/* is sacrosanct. Currently I think the sacrosanct status of /home/* for rpm should be probably really enforced by default. In general: When you fully trust a third party (i.e. when you allow that third party to work as root on your system), you can install their RPMs "as usual" (i.e. without such a profile). Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org