After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 777999 - NetworkManager requires auth parameter to be set when tls-auth is used
NetworkManager requires auth parameter to be set when tls-auth is used
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: VPN: openvpn
1.6.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks: nm-openvpn-options
 
 
Reported: 2017-01-31 19:17 UTC by Karol Babioch
Modified: 2020-11-12 14:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Karol Babioch 2017-01-31 19:17:53 UTC
NetworkManager requires the "auth" parameter to be set when using the "tls-auth" parameter. When providing a tls-auth secret using the applet, but leaving the auth parameter blank, an error message is produced:

ERROR: tls-auth enabled, but no valid --auth algorithm specified ('none')

This probably made sense with older OpenVPN versions, but starting with OpenVPN 2.4 GCM ciphers can be used, which will not only encrypt, but also authenticate packages, making the auth parameter obsolote in cases it is used.

I.e. it is perfectly fine to "tls-auth", but no "auth" in combination with an AES-XXX-GCM cipher. Therefore NetworkManager should not quit with an error message, but allow for such a configuration. It works perfectly with with OpenVPN itself, so NetworkManager should not try to be outsmart OpenVPN at this point, since it renders it useless.
Comment 1 André Klapper 2020-11-12 14:27:47 UTC
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).