Hi, On Mon, Aug 15, 2022 at 12:40:55PM +0200, Timo Rothenpieler wrote: > Add checks for ifconfig-noexec + route-noexec being set, and either only > warn in that case,
... this is what I suggested two mails upthread :-)
> or don't even try to retain capabilities, since
> they're not needed either way. I'd prefer the later, since fewer
> capabilities is generally better.
I could see arguments for "we want to do the ifconfig/route setup in
an --up script" - for example to do VRF/NetNS stuff that OpenVPN can not
do itself. So for these scenarios having the capability around would
be useful (= thus, try-and-warn)...
Different scenario, same options. We don't always know what users want.
> implementing them. Shouldn't be that hard, given the config is already
> there.
> I don't have a NM setup to test that on though.
Sending to the debian bug report referenced upthread and asking them
to test might be an option here. Or ask David.
I do not use NM either.
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany g...@greenie.muc.de
signature.asc
Description: PGP signature
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
