Since it would never (rarely?) work in a container anyway I'm not sure about
the "real" need to SRU this, but fixing in 19.04 onwards seems right to me.
Furthermore anyone could fix it by changing the config like
$ echo "/usr/lib/ipsec/stroke rmix," | sudo tee
/etc/apparmor.d/local/usr.lib.ipsec.stroke
Please @Andreas Dosztal - is there a real "in container" use case for
this or were you just playing with it when you found the bug?
** Changed in: strongswan (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: strongswan (Ubuntu Cosmic)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780534
Title:
Default usr.lib.ipsec.stroke profile causes segfault for 'ipsec
status'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1780534/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
