[Bug 606365]

[Psychonaut]

(In reply to Dennis Schridde from comment #14)
> Does the import work when using nmcli (`nmcli connection import type openvpn
> file $FILENAME`)?
> 
> If nmcli works, I would think this is mostly caused by Plasma NM not using
> the NetworkManager OpenVPN code to import configuration files (bug #396530),
> but implements an own buggy version.

I'm now using plasma-nm 5.12.8.  This version has the same behaviour as
described for plasma-nm 5.12.6 in Comment 13: attempting to import an
.ovpn file with inline certificates and keys results in a spurious error
dialog, but the keys and certificates get successfully copied anyway.

I also tried using nmcli.  This seems to work without any problems:

$ nmcli connection import type openvpn file ~/vpn/ukp-vpn.ovpn 
Connection 'ukp-vpn' (c6cbabfe-f117-4af9-aca5-be9e8c88595c) successfully added.

When I open the NetworkManager plasma applet after doing this, I see the
VPN connection listed there, with the keys and certificates copied into
separate files under ~/.cert/nm-openvpn.

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-nm in Ubuntu.
https://bugs.launchpad.net/bugs/606365

Title:
  unable to import config with inlined ca, cert, key or tls-auth

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/606365/+subscriptions