This bug was fixed in the package apparmor - 4.1.0~beta5-0ubuntu8
---------------
apparmor (4.1.0~beta5-0ubuntu8) plucky; urgency=medium
* Add a patch to allow OpenVPN access to the systemd notify socket
(LP: #2101796):
- d/p/u/openvpn-systemd-notify.patch
* Add a patch to allow OpenVPN to read NetworkManager imported certs
(LP: #2101909):
- d/p/u/openvpn-networkmanager-imports.patch
* Add a patch to allow utils to parse the fusermount profile
(LP: #2101869):
- d/p/u/utils-fix-mount-handling-hyphens.patch
apparmor (4.1.0~beta5-0ubuntu7) plucky; urgency=medium
* Add patch to add os-prober and linux-boot-prober profiles
(LP: #2099811):
- d/p/u/os_prober_mr_1569.patch
* debian/apparmor.install: add entries for the os-prober and
linux-boot-prober profiles
-- Ryan Lee <ryan....@canonical.com> Mon, 10 Mar 2025 09:43:48 -0700
** Changed in: apparmor (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2101909
Title:
AppArmor OpenVPN profile blocks access to NetworkManager-OpenVPN
imported certs
Status in apparmor package in Ubuntu:
Fix Released
Bug description:
The openvpn profile shipped in the AppArmor package in Plucky
(4.1.0~beta5-0ubuntu6 as of time of writing) does not allow access to
the ~/.cert/nm-openvpn, which is needed to allow OpenVPN to use
certificate files imported by NetworkManager. This was reported by
"@zorn-v" upstream as a comment on
https://gitlab.com/apparmor/apparmor/-/merge_requests/1263.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2101909/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
