diff options
| author | Gerald Turner <gturner@unzane.com> | 2017-05-11 17:15:09 -0700 |
|---|---|---|
| committer | Yves-Alexis Perez <corsac@corsac.net> | 2017-06-30 13:52:01 +0200 |
| commit | b8ac1d49802dbadecb1805baf4d6ca0ac7735ef0 (patch) | |
| tree | 27e0c6b8e2deedf49416a40a933a7f22b8174cec /debian/charon-systemd.install | |
| parent | 784751a50713ae63faeb9aac3b0d77581324e70e (diff) | |
| download | vyos-strongswan-b8ac1d49802dbadecb1805baf4d6ca0ac7735ef0.tar.gz vyos-strongswan-b8ac1d49802dbadecb1805baf4d6ca0ac7735ef0.zip | |
Install AppArmor profiles for /usr/sbin/swanctl and /usr/sbin/charon-systemd.
The AppArmor profile for charon-systemd was copied from the existing
profile for /usr/lib/ipsec/charon without much scrutiny other than
testing basic IPsec tunnels (no fancy plugin options were tested). It
appears that the team at Canonical that had written the
/usr/lib/ipsec/charon policy had done extensive testing with several
plugins, and it seems likely that applying the same profile to
charon-systemd will allow those plugins to continue to work.
The AppArmor profile for swanctl was written from scratch and well
tested. It turns out that swanctl unnecessarily loads plugins by
default, so a bit of frivolous access has been granted.
Diffstat (limited to 'debian/charon-systemd.install')
| -rw-r--r-- | debian/charon-systemd.install | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/debian/charon-systemd.install b/debian/charon-systemd.install index 6ab3af8f1..a1424ab88 100644 --- a/debian/charon-systemd.install +++ b/debian/charon-systemd.install @@ -2,3 +2,4 @@ etc/strongswan.d/charon-systemd.conf lib/systemd/system/strongswan-swanctl.service usr/sbin/charon-systemd usr/share/strongswan/templates/config/strongswan.d/charon-systemd.conf +debian/usr.sbin.charon-systemd /etc/apparmor.d/ |