Move the functionality of /var/lib/snapd/system-params to its own package with unit tests, to get a more structured approach to the file.
Let SetupSnapConfineSnippets itself discover the homedirs instead of passing it as a parameter, this is also more in line with how it already functions with existing features.
Each serial driver can leave its own file specifying harware
information in /proc/tty/driver/, in the same format as "serial"
driver, so we should allow reading any of them. Example of files
created there are usbserial, max310x or IMX-uart.
The ibus input method communicates via a private D-Bus message bus
implemented with glib's D-Bus implementation. With glib >= 2.75.0, this
switched from an abstract namespace unix socket to a regular unix
socket. This commit grants access to the regular unix socket path.
https://launchpad.net/bugs/2008279
udisks2 which use the C polkit library, does not send calls to the
peer name but to the peer address directly. So AppArmor can not
properly filter based on peer name.
This interface makes it possible to control MicroOVN.
It will be used by another snap, MicroCloud to bring up MicroOVN
and LXD clusters automatically.
Signed-off-by: Stéphane Graber <stgraber@ubuntu.com>
* interfaces: relax rules for mount-control `what` for functionfs
The `functionfs` `what` rules are too strict. With functionfs
pretty much anything can be in the `what` line so best to not
bother, especially since functionfs requires a explicit mention
in the plug declaration.
* interfaces: refactor so that validateWhatAttr can take more things into consideration
* interfaces: do not allow AppArmorRegex in "what"
* interfaces: improve the error message when functionfs is used
