GNOME Bugzilla – Bug 754394
nm-connection-editor segfaults when importing .ovpn config
Last modified: 2015-09-07 08:17:18 UTC
Hi all, this is a duplicate of #726935 filed in Debian [0] and I just managed to reproduce it on testing with the following network-manager packages installed from unstable: --- snip --- ii network-manager 1.0.6-1 amd64 network management framework (daemon and userspace tools) ii network-manager-gnome 1.0.6-1 amd64 network management framework (GNOME frontend) ii network-manager-openvpn 1.0.6-1 amd64 network management framework (OpenVPN plugin core) ii network-manager-openvpn-gnome 1.0.6-1 amd64 network management framework (OpenVPN plugin GNOME GUI) --- snip --- The exact symptoms are that nm-connection-editor segfaults with a message such as: nm-connection-e[15204]: segfault at 0 ip (null) sp 00007fffb3d6d848 error 14 in nm-connection-editor[400000+5a000] whenever I try to import a OpenVPN configuration file. A patch for this seems to have been distributed with the Ubuntu packaging [0] and can be found on [1]. I am not sure why this has neither been reported upstream so far nor fixed in Debian, but that seems to be the case right now. [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726935 [1] https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1294899 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;msg=25;filename=11-user-connections.patch;bug=726935
This is not an upstream issue, but due to a Debian specific patch. So there is nothing upstream can do about this.
If you experience a crash in 1.0.6 its quite possibly a different issue. Best would be if you attach the ovpn file that triggers the issue. Beware of stripping private data (in a way so that the crash still happens).
The following configuration has been stripped of private data, but still results in the aforementioned behaviour: --- snip --- dev foovpn1 dev-type tun remote vpn.example.com 12001 lport 12001 client persist-key persist-tun comp-lzo verb 3 user nobody group nogroup keepalive 10 120 remote-cert-tls server tls-client <ca> -----BEGIN CERTIFICATE----- ca_cert_content -----END CERTIFICATE----- </ca> <cert> -----BEGIN CERTIFICATE----- cert_content -----END CERTIFICATE----- </cert> <key> -----BEGIN PRIVATE KEY----- key_content -----END PRIVATE KEY----- </key> <tls-auth> -----BEGIN OpenVPN Static key V1----- tls_auth_content -----END OpenVPN Static key V1----- </tls-auth> --- snip --- I could also reproduce it with a file in which certificates are referenced explicitly and not inlined.
This bug has, apparently, been fixed in Debian (cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726935#50 )