I got another finding about the question why openvpn could refuse to work with cyberghostvpn cli utility.
I followed the support instructions to manually estabilish an openvpn connection.
If I download my personal openvpn configuration the openvpn.ovpn file contains a setting that is deprecated since openvpn 2.6: ncp-disable
$ sudo openvpn openvpn.ovpn
Options error: Unrecognized option or missing or extra parameter(s) in openvpn.ovpn:12: ncp-disable (2.6.1)
If I remove the ncp-disable line from the openvpn.ovpn configuration file I am able to manually fire up openvpn and successfully connect to a cyberghost vpn server.
Pinned Comments
moormaster commented on 2024-08-09 22:32 (UTC) (edited on 2024-08-09 22:33 (UTC) by moormaster)
The problems connecting to openvpn are unrelated to the kernel version. They occur if one uses the updated default
/etc/sudoers
content.There has been an update recently: https://gitlab.archlinux.org/archlinux/packaging/packages/sudo/-/commit/4791df5c3deb6355e6a1fe0b40a13ef27ad060b0
that changes
to
Activating the
secure_path
setting will prevent cyberghostvpn from running the /usr/local/cyberghost/openvpn wrapper. This means the original/usr/bin/openvpn
wrapper gets called with the unsupported--ncp-disable
parameter again - and fails.To make cyberghostvpn work again with openvpn
a) either comment out the
Defaults secure_path=...
line in /etc/sudoers againb) or add
/usr/local/cyberghost
to the beginning of that line/etc/sudoers
c) or downgrade openvpn to <2.6 - that makes it support the
--ncp-disable
command line parameter again