| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| tests-Explicitly-unshare-userns-when-testing-disable-user.patch | tests: Explicitly unshare userns when testing --disable-userns If we're running the tests as uid 0 with capabilities, then bwrap will not create a new user namespace by default, which means the limit won't be exceeded and the test will fail. Make sure we always try to create the new user namespace. |
Simon McVittie <smcv@collabora.com> | yes | 2023-02-23 | ||
| tests-Try-harder-to-evade-disable-userns.patch | tests: Try harder to evade --disable-userns The worst-case scenario in terms of enforcing --disable-userns is that we're retaining all capabilities, so test that too, to make sure that the option is genuinely restricting even a privileged user. |
Simon McVittie <smcv@collabora.com> | yes | 2023-02-23 | ||
| debian/Change-EPERM-error-message-to-show-Debian-specific-inform.patch | Change EPERM error message to show Debian-specific information | Simon McVittie <smcv@debian.org> | not-needed | 2021-01-01 |