2015... Nothing was done yet. Let's make some movements. Here is the import function: http://bazaar.launchpad.net/~network-manager/network-manager-openvpn/trunk/view/head:/properties/import-export.c#L268
and here are the lines of ca/cert/key tags parsing: http://bazaar.launchpad.net/~network-manager/network-manager-openvpn/trunk/view/head:/properties/import-export.c#L563 My suggestion is to save inline ca/cert/key inside of a Network Manager configurations file encoded into base64 (again) with "inline:" prefix, e.g.: [connection] id=MyVPN uuid=ac9d354e-03ef-4063-8c96-4a40bd17bea6 type=vpn [vpn] service-type=org.freedesktop.NetworkManager.openvpn connection-type=tls remote=myvpnhost.com cert-pass-flags=0 tap-dev=no proto-tcp=no mssfix=no ca=inline:<base64 coded> cert=inline:<base64 coded> key=inline:<base64 coded> Another approach would be to parse as much information from *.ovpn file as we can, remove parsed parts, encode rest of the file into a base64 string, and save it into a Network Manager connection config file. This may help to deal with extra options like inline certificates, but may also cause unexpected configuration conflicts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
