Launchpad has imported 14 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=349282.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2015-06-17T10:03:22+00:00 Psychonaut wrote: The Connection Editor of the NetworkManager plasma applet is unable to import OpenVPN configuration files which contain inline certificates and keys. Reproducible: Always Steps to Reproduce: 1. Open the Connection Editor. 2. File -> Import VPN… 3. Select and open an OpenVPN configuration file (.ovpn) which contains inline certificates and/or keys. That is, the file specifies "[inline]" as the value of the ca, cert, key, and/or tls-auth fields, and then provides ASCII-armoured certificates and/or keys in <ca>, <cert>, <key>, and <tls-auth> elements at the end of the file. Actual Results: 4. For every inline certificate/key in the configuration file, an error dialog appears indicating that the certificate/key could not be copied because the file [inline] could not be opened. For example: Error copying file to /home/miller/.kde4/share/apps/networkmanagement/certificates/ukp- vpn_[inline]: Cannot open /tmp/[inline] for input Expected Results: 4. The Connection Editor should recognize that "[inline]" is not a filename but rather a special value indicating that the certificate/key is contained within the OpenVPN configuration file itself. It should then read in and process that certificate/key. Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/606365/comments/36 ------------------------------------------------------------------------ On 2015-06-19T07:51:58+00:00 Jgrulich wrote: Do you really use plasma-nm in version 0.9.3.4? I thought this has been fixed already. Any chance you can try at least 0.9.3.5 version where I did one more fix regarding OpenVPN import. Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/606365/comments/37 ------------------------------------------------------------------------ On 2015-06-19T08:22:53+00:00 Psychonaut wrote: Yes, I'm running plasma-nm 0.9.3.4. I can't test 0.9.3.5 at the moment but can do so as soon as it's packaged for openSUSE 13.2. Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/606365/comments/38 ------------------------------------------------------------------------ On 2015-06-28T15:16:13+00:00 Lamarque wrote: That is not the syntax our import code expects. The import code expects no ca, cert, key or ts-auth tags with '[inline]' as value when certificates are embedded. It expects only <ca>, <cert> <key> and <tls- auth> tags in that case. Besides, using '[inline]' as value is redundant in this case. Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/606365/comments/39 ------------------------------------------------------------------------ On 2015-06-28T18:46:05+00:00 Psychonaut wrote: It may not be the syntax the plasma-nm import code expects, but it's one that the OpenVPN command-line client supports. I've come across a few .ovpn files which use this syntax, and I've seen it recommended by OpenVPN experts such as Jan Just Keijser (see for example <http ://openvpn-users.narkive.com/ZwzahkCv/embedding-key-cert-ca-into-client- config>). It looks like this [inline] directive was never documented in the OpenVPN man pages. However, given that it's in use, it might still be a good idea for plasma-nm to handle this syntax. Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/606365/comments/40 ------------------------------------------------------------------------ On 2015-06-28T23:28:46+00:00 Lamarque wrote: Git commit 599afdacd744a2d7785274687438a23f21617c34 by Lamarque V. Souza. Committed on 28/06/2015 at 23:26. Pushed by lvsouza into branch 'master'. Add support to import .ovpn files with syntax described in http://openvpn-users.narkive.com/ZwzahkCv/embedding-key-cert-ca-into-client-config FIXED-IN: 0.9.3.7 M +22 -5 vpn/openvpn/openvpn.cpp http://commits.kde.org/plasma- nm/599afdacd744a2d7785274687438a23f21617c34 Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/606365/comments/41 ------------------------------------------------------------------------ On 2015-06-29T01:03:02+00:00 Lamarque wrote: Git commit c6f0b9df0e1a78c4d54058136580104b5e5b22a7 by Lamarque V. Souza. Committed on 29/06/2015 at 00:21. Pushed by lvsouza into branch '0.9.3'. Add support to import .ovpn files with syntax described in http://openvpn-users.narkive.com/ZwzahkCv/embedding-key-cert-ca-into-client-config FIXED-IN: 0.9.3.7 M +22 -5 vpn/openvpn/openvpn.cpp http://commits.kde.org/plasma- nm/c6f0b9df0e1a78c4d54058136580104b5e5b22a7 Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/606365/comments/42 ------------------------------------------------------------------------ On 2017-08-20T13:19:02+00:00 Psychonaut wrote: Still reproducible for me with plsma-nm 5.10.4. I get the following error dialog when importing configuration files with inline certificates and agreeing with the prompt to copy the certificates to ~/.local: Error copying certificate to /home/psy/.local/share/networkmanagement/certificates/ukp-vpn_[inline]: Cannot open /home/psy/vpn/UKP/[inline] for input Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/606365/comments/100 ------------------------------------------------------------------------ On 2017-08-20T13:22:39+00:00 Psychonaut wrote: I should add that despite the error message, plasma-nm successfully extracted the certificates and copied them to ~.local/share/networkmanagement/certificates. So maybe the error message is spurious. Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/606365/comments/101 ------------------------------------------------------------------------ On 2017-08-20T14:07:23+00:00 Lamarque wrote: Hi. Hmmm QFile was not able to open the source file (/home/psy/vpn/UKP/[inline]). Does your user has permission to open that file for reading? That error message is shown only if QFile::copy returns false [1] If the destination file already exists then QFile::copy returns false. That can be the problem too. In that case QFile::copy does not override the destination file. Probably we should ask the user if he/she wants to override it or keep the old one. [1] http://doc.qt.io/qt-5/qfile.html#copy OBS: since Plasma NM was not able to copy the file what it does is registering the source file's path (/home/psy/vpn/UKP/[inline]) in NetworkManager. Since NetworkManager run as root it probably has permission to read that file. OBS2: Plasma NM run as normal user. Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/606365/comments/102 ------------------------------------------------------------------------ On 2017-08-20T14:37:08+00:00 Psychonaut wrote: (In reply to Lamarque V. Souza from comment #9) > Hi. Hmmm QFile was not able to open the source file > (/home/psy/vpn/UKP/[inline]). Does your user has permission to open that > file for reading? That error message is shown only if QFile::copy returns > false [1] That's because the file doesn't exist. As I already mentioned in the original report, plasma-nm is misinterpreting the [infile] header in the .ovpn file as a filename. It should not be trying to open any new files; the certificates should be read from the .ovpn file it already has open. Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/606365/comments/103 ------------------------------------------------------------------------ On 2017-08-20T15:50:24+00:00 Lamarque wrote: Does your file name has any space in it? If it does then you must use quotation mark in the .ovpn to delimitate the file name. Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/606365/comments/104 ------------------------------------------------------------------------ On 2017-08-20T18:16:50+00:00 Psychonaut wrote: (In reply to Lamarque V. Souza from comment #11) > Does your file name has any space in it? If it does then you must use > quotation mark in the .ovpn to delimitate the file name. I'm telling you for the third time, there is no filename in the .ovpn file. This bug report is about plasma-nm's failure to process .ovpn files which use the special identifier "[inline]" to indicate that the certificates and/or keys are included directly in the .ovpn file. Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/606365/comments/105 ------------------------------------------------------------------------ On 2018-10-24T07:13:16+00:00 Psychonaut wrote: Still reproducible as discussed in Comment 7 and Comment 8 with plasma- nm 5.12.6. That is, importing an OpenVPN configuration file with inline certificates and keys throws up a spurious error dialog about being unable to open the nonexistent file named "[inline]". However, the certificates and keys get successfully copied anyway. Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/606365/comments/109 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/606365 Title: unable to import config with inlined ca, cert, key or tls-auth Status in NetworkManager-OpenVPN: Fix Released Status in plasma-nm: New Status in network-manager-openvpn package in Ubuntu: Fix Released Status in plasma-nm package in Ubuntu: Fix Released Bug description: Binary package hint: network-manager-openvpn-gnome So a client of mine runs an OpenVPN setup. It exported a client.ovpn file but it fails to completely import this file using the network- manager (gnome) on Ubuntu 10.04. When I import the file, it gives me the name ("client") and gateway ("vpn.example.org") on the initial screen. No other fields are populated even though the client.ovpn file also includes a user certificate, server certifikate and a private key. When I go to advanced, some (most) of the settings obviously seem to import correct, others not at all. E.g. none of the TLS settings (key and key direction) are imported. From what I understand I should be able to use this without any additional settings. The following software is installed through aptitude: * openvpn (2.1.0) * openvpn-blacklist * network-manager-openvpn * network-manager-openvpn-gnome To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/606365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
