Description of problem: OpenVPN connections are not chrooted. Relevant log line when connecting to any OpenVPN server. <warn> Directory '/var/lib/openvpn/chroot' not usable for chroot by 'nm-openvpn', openvpn will not be chrooted. Additional info: Creating the directory /var/lib/openvpn/chroot and setting nm-openvpn as owner and group does not make a difference. This probably also needs changes to the selinux configuration.
for this to work, you also need a directory /var/lib/openvpn/chroot/tmp, see https://git.gnome.org/browse/network-manager-openvpn/tree/src/nm-openvpn-service.c?id=e1fa810171a6a46bde9752f00a96f590c53ccb62#n1079 I think, it's a bug (missing feature) in the Fedora package, which should create these directories on package install.
there is also bug 922786 which seems related.
I think upstream nm-openvpn plugin should get smarter and create the chroot environment as needed
WIP at https://git.gnome.org/browse/network-manager-openvpn/commit/?h=th/chroot-rh1377708 I am not sure, that we can enable chroot in general.
> service: create runstate dir for management socket +static char * +mgt_path_create (NMConnection *connection, GError **error) +{ + int errsv; + gs_free char *s = NULL; + + /* Setup runtime directory */ + if (g_mkdir_with_parents (RUNDIR, 0755) != 0) { + errsv = errno; + if (errsv != EEXIST) { g_mkdir_with_parents() returns 0 if the directory already exists, so this last check is not needed? The rest (excluding last WIP commit) LGTM.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.