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 719429 - parsing .ovpn with "auth-user-pass" results in another (wrong) authentication
parsing .ovpn with "auth-user-pass" results in another (wrong) authentication
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: VPN: openvpn
unspecified
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks: nm-openvpn-options
 
 
Reported: 2013-11-27 15:29 UTC by Colin Macdonald
Modified: 2016-03-31 10:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
example_sanitized.ovpn (426 bytes, application/octet-stream)
2013-11-27 15:29 UTC, Colin Macdonald
Details

Description Colin Macdonald 2013-11-27 15:29:20 UTC
Created attachment 262952 [details]
example_sanitized.ovpn

When I load a .ovpn file which should use username/password authentication, the NetworkManager GUI** presents "Authentication Type" as "Certificates (TLS)".

(**: or gnome3, not sure which bits do what anymore!)

I will attach an example.

Relevant versions:

NetworkManager.x86_64  1:0.9.9.0-19.git20131003.fc20
openvpn.x86_64         2.3.2-4.fc20

Additionally, inline cert's aren't used.  But this is already reported as bug #633337.

My administrator says:

> I don't think we can do anything about this. It's the parser of the
> client application which needs to parse these things correctly. We
> are doing username/password auth rather then certificate auth, so
> it needs to be able to interpret that option. If you find a version
> of the config file that it would parse correctly, I can then update
> it on the web.
Comment 1 Thomas Haller 2016-03-31 10:52:08 UTC
This seems to be fixed -- at least on master/1.2-beta3



$ nmcli connection import type openvpn file ./example_sanitized.ovpn 

results in


# cat /etc/NetworkManager/system-connections/example_sanitized
[connection]
id=example_sanitized
uuid=5165e128-c183-4bbe-96a8-fc63d24fad75
type=vpn
permissions=
secondaries=

[vpn]
ping=10
connection-type=password
password-flags=1
remote=san.it.ized.org
comp-lzo=yes
ping-restart=60
ca=/home/user/.cert/nm-openvpn/example_sanitized-ca.pem
dev=tap0
service-type=org.freedesktop.NetworkManager.openvpn

[ipv4]
dns-search=
method=auto

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=auto



and nm-connection-editor shows "Authentication Type" as "Password".
Same via nm-connection-editor's import.


Closing. Please re-open if you have further issues. Thank you.



btw, inline certificates (bug 633337) work now too.