According to the OpenVPN wiki [0]:
- openvpn@.service is deprecated.
- openvpn.service is obsoleted. (This is only used for backward
compatibility)
The openvpn-client@ and openvpn-server@ units worked very nicely for me,
is it possible to add a header to both units to point to the recommended
Control: clone 866523 -2
Control: retitle -2 Upstream systemd unit has too limited
CapabilityBoundingSet
Control: forwarded -2 https://community.openvpn.net/openvpn/ticket/918
Cloned into seperate bug for the limited bounding set
Bernhard,
> Unfortunately I'm a total DAC illiterate, can anyone explain the
> difference between
>
> Upstream:
> CAP_DAC_OVERRIDE
>
> Debian:
> CAP_DAC_READ_SEARCH CAP_AUDIT_WRITE
>
> and what they actually mean? What is allowed by the Debian unit that
> is not allowed by the Upstream unit, an
Control: tags -1 + upstream
Hi,
> This bug hit me pretty hard. I unknowingly used the upstream
> openvpn-server@ unit, and then spent a day or so trying to work out why
> it did not work – the upstream one has CAP_AUDIT_WRITE missing from its
> capability list.
>
> Perhaps the upstream one could
This bug hit me pretty hard. I unknowingly used the upstream openvpn-server@
unit, and then spent a day or so trying to work out why it did not work - the
upstream one has CAP_AUDIT_WRITE missing from its capability list.
Perhaps the upstream one could be patched to include this capability?
Package: openvpn
Version: 2.4~rc1-1
Severity: important
Since 2.4~rc1-1 the OpenVPN binary package ships two additional systemd
units from upstream
/lib/systemd/system/openvpn-client@.service
/lib/systemd/system/openvpn-server@.service
in addition to the ones that are Debian specific
/lib/syste
6 matches
Mail list logo
