Can you specify why exactly the systemd approach would need access to /etc/wireguard? The keys are a valid argument (but could be placed somewhere else). Anything else that it needs from this directory?
When configuring a WireGuard tunnel through Netplan, it also creates a systemd netdev and AFAIK it never got in conflict with /etc/wireguard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2091987 Title: group and mode of /etc/wireguard incompatible with systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/2091987/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
