VPN Providers are using OVPN files more often because you can bundle the certificates and configuration into one file making them more relevant.
Last time I checked, the Import feature simply extracted supported values and loaded them into the application? The problem with that approach is OpenVPN is developed faster than network-manager-openvpn which means if network-m anager-openvpn lags behind in supporting OpenVPN parameters, you're still left in a situation where you simply can't use it. By simply specifying a OVPN file which is then just directly passed to OpenVPN as an argument without the same sort of processing, you can bypass this problem and enjoy the benefits of the UI and integration network-manager-openvpn brings. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1047362 Title: Allow specifying an existing ovpn file instead of using the GUI for options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1047362/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
