resync charon apparmor profiles
Bug #1807664 reported by
Christian Ehrhardt
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| strongswan (Ubuntu) |
Fix Released
|
Undecided
|
Christian Ehrhardt | ||
Bug Description
There are two ways to start charon at the moment.
Depending which is used there are different apparmor profiles.
We should re-sync both to pick up fixes that were done in "the other" one in recent history.
Related branches
~paelzer/ubuntu/+source/strongswan:merge-disco-5.7.1-1-ubuntu2
Merged
into
ubuntu/+source/strongswan:ubuntu/disco-devel
at
revision 891ab057597eb2f27dbc7328e009f8179a1f0465
- Andreas Hasenack: Approve
- Canonical Server packageset reviewers: Pending requested
- git-ubuntu developers: Pending requested
-
Diff: 81 lines (+26/-2)4 files modifieddebian/changelog (+10/-0)
debian/usr.lib.ipsec.charon (+7/-0)
debian/usr.sbin.charon-systemd (+6/-2)
debian/usr.sbin.swanctl (+3/-0)
| Changed in strongswan (Ubuntu): | |
| status: | New → In Progress |
| assignee: | nobody → Christian Ehrhardt (paelzer) |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in strongswan (Ubuntu): | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
This bug was fixed in the package strongswan - 5.7.1-1ubuntu2
---------------
strongswan (5.7.1-1ubuntu2) disco; urgency=medium
* d/usr.sbin.
path (LP: #1773956)
* d/usr.lib.
profiles of both ways to start charon (LP: #1807664)
* d/usr.sbin.swanctl: add apparmor rule for af-alg plugin (LP: #1807962)
-- Christian Ehrhardt <email address hidden> Mon, 10 Dec 2018 08:30:01 +0100