OpenVPN network-manager does not correctly import .crt and .key files when importing .ovpn file, instead it will import a useless .pem file
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
When importing .ovpn file from a provider in network-manager, Under VPN tab > it auto-populates the CA Certificate field with a default .pem file which i am not sure where it even found that.
Also under VPN > Advanced > Key File - it would auto-populate the field with a .pem as well.
Are these .pem files system generated? because it surely does not come from the .ovpn file itself.
It is true that the .ovpn file includes both the .crt and .key within the file.ovpn, because from Terminal it connects perfectly and does not require an external .crt and .key to be included in the command # openvpn vpnserver.
OpenVPN does not correctly import .crt and .key files when importing .ovpn file in network-manager, This makes it difficult for the user when importing many vpn servers, to go to the CA and tls key field and import the correct certificates manually everytime.
Whats supposed to happen is, Network-Manager is supposed to import the CA and tls key correctly which come from the .ovpn file itself once .ovpn file gets imported.
Can this be fixed?
On a side note: it would be heavily appreciated if network-manager is able to mass import all .ovpn files at once correctly WITH ca and tls keys in place.
At the moment, it is to my understanding that there is not even a way to backup ovpn profiles and to import them backup all at once to a new PC. Everything has to be done manually. Hope this can be included in the bug fix.
