** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970455
Title:
AppArmor profile prevents DNS Servers from being added to resolv.conf
To manage notifications
The resolve plugin only writes directly to resolv.conf if resolvconf is
not available (see
https://docs.strongswan.org/docs/5.9/plugins/resolve.html for details).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is my take on this:
- we have a DEP8 test that creates a strongswan vpn, and I haven't seen this
error there
- that tells me that it's only certain configurations that trigger this
(confirming what it's said in the bug description)
- should we allow writing to resolv.conf in all cases?
@server-triage-discuss - looks like there may have been some discussion
on this when I wasn't around. Did this mean to get dropped? If so, let's
set as Won't Fix.
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for taking the time to report this bug, Sebastian.
I'm adding it to the Ubuntu Server queue; as you mentioned, this is a
relatively old issue and IIUC there's been some pushback to implement
this. As Christian mentioned in the Debian bug, enabling write access
via the apparmor profile by
** Changed in: strongswan (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970455
Title:
AppArmor profile prevents DNS Servers from being added to resolv.conf
** Bug watch added: Debian Bug tracker #915147
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915147
** Also affects: strongswan (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915147
Importance: Unknown
Status: Unknown
--
You received this bug notification
