Repository navigation
Hotfix
This hotfix lets users migrate from 4.0.2. We previously accepted any policy version, and we blocked that in v4.3.0 with a "config sanity" objective, but it locked people out when they upgraded with apt.
If you are locked out with 4.3.0 today, run su -c '/usr/sbin/dpkg-reconfigure dosr' (or with another privileged tool). Then you can apt upgrade to 4.3.1 without worries.
Now, when Debian users run dosr apt upgrade, RootAsRole does not upgrade the policy content by itself, because the process does not hold CAP_LINUX_IMMUTABLE. It is a first barrier that prevents the policy from being modified directly by the apt process; it can still be bypassed in 2-steps, though. But that is way more noticeable than inside the apt process, which is usually overly trusted. With this v4.3.1 hotfix, dosr still accepts the old policy, but applies the upgrade in memory and logs a warning in the journal.
So when a policy file upgrade has to be done, only dosr chsr upgrade should be allowed to do it. We'll try to avoid cases where the file has to be modified by an upgrade.
We are working on updating the documentation and on ways to enforce the integrity of RaR. Soon.