[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
** Changed in: plasma-nm
Status: New => Fix Released
--
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:
Fix Released
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
Made a script to split a single OpenVPN file to multiple to avoid the issue due
to XML chunks within the single file breaking network-manager-openvpn when
importing
https://gist.github.com/ThomasG77/5c09eead1244f9d1d2bd7fa70b26fead
--
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
I am having the same issue on Ubuntu 18.04 LTS.
sudo nmcli connection import type openvpn file config.ovpn
gives the following error
Error: failed to import 'config.ovpn': configuration error: unsupported 3th
argument net_gateway to “route” (line 12).
Running
sudo openvpn config.ovpn
works
--
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
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 , , , and 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 , and 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 ). 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 -5vpn/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 -5vpn/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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
I was able to solve my problems on Ubuntu Mate 18.04 by using the
command line (rather than the network manager gui) to import the .ovpn
as follows:
User@Node-99:~/Downloads$ sudo nmcli connection import type openvpn file
Miami.ovpn
Error: failed to import 'Miami.ovpn': configuration error: invalid 1th
argument to “mssfix” where number expected (line 6).
What is good about the command line is that it is more verbose and will
help you find which line in your .ovpn file is causing the error.
In my case I used a text editor to open the file Miami.ovpn and I
commented out the offending line (It was line 6)
So I placed a # in front of the line and a space.
After doing that:
User@Node-99:~/Downloads$ sudo nmcli connection import type openvpn file
Miami.ovpn
Connection 'Miami' (cb4d9379-9f35-4b03-b53d-3af05781e5aa) successfully added.
Problem solved. VPN able to connect now and it shows up as a choice
inside of the Network manager.
--
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
My ubuntu 16.04 has affected but #77 fixed it.
--
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
Just experienced this issue in Ubuntu 17.04. Manually configuring the
key-direction as stated in #76 fixed it.
--
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
** Changed in: plasma-nm
Status: Unknown => New
** Changed in: plasma-nm
Importance: Unknown => High
--
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
plasma-nm was fixed in Wily with https://launchpad.net/ubuntu/+source
/plasma-nm/4:5.3.95-0ubuntu1
** Also affects: plasma-nm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: plasma-nm (Ubuntu)
Importance: Undecided => Medium
** Changed in: network-manager-openvpn (Ubuntu)
Importance: High => Medium
** Changed in: plasma-nm (Ubuntu)
Status: New => Fix Released
--
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:
Unknown
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
network-manager-openvpn was fixed in Xenial with
https://launchpad.net/ubuntu/+source/network-manager-openvpn/1.1.93-1
--
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:
Unknown
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
The original bug as reported was a failure to import certain
configuration files using network-mangaer-openvpn. This turned out to be
due to the use of inlined key material (comment 24). network-manager-
openvpn did not support this as a feature at the time, so was unable to
parse this type of configuration file.
Support was since added (comment 46). This has been confirmed to work
(comments 49, 63, 67, 68 etc). Therefore, this bug as reported has been
fixed, so I'm setting it to Fix Released.
It may well be that this doesn't solve configuration imports for all
users, as is clear from subsequent comments. But we track one issue per
bug, since otherwise statements like "this bug is fixed" and "this bug
is not fixed" become meaningless, developers cannot track what they are
being asked to do, and users end up with wildly varying expectations
that can never be met.
Note that a failure to import a configuration can be an entire class of
bugs, not just one single bug. This bug's original reporter's problem
turned out to be "doesn't work with inlined key material". Clearly
that's not the only thing wrong here, as adding inlined key material
support solved the problem for some, but not others. Of the remaining
users here who still have import problems, there may yet be *multiple*
underlying bugs. So please don't all pile on to a different bug thinking
you're still all affected by the same issue.
If you'd like to see your problem fixed, and you'd like to help, then
first please read "How to Report Bugs Effectively"
(https://www.chiark.greenend.org.uk/~sgtatham/bugs.html) carefully. Take
some time to work out exact steps to reproduce your problem, make sure
that they really do reproduce, and then paste exact and detailed
instructions on how to reproduce your problem into a new bug report.
Don't assume that someone else's import failure problem is due to the
same underlying bug as your import failure problem. Do link to bugs that
you think may be related (such as this one). Don't worry about filing
duplicates; in this kind of case it takes far more effort to untangle
reports that turn out to have different root causes then it does to mark
duplicate bugs if this becomes clear to developers later.
I hope this helps. I can't guarantee what will come next, but by filing
actionable reports at least you'll be one step closer to real progress.
** Changed in: network-manager-openvpn (Ubuntu)
Status: Confirmed => Fix Released
--
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:
Unknown
Status in network-manager-openvpn 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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
** Bug watch added: KDE Bug Tracking System #349282
https://bugs.kde.org/show_bug.cgi?id=349282
** Package changed: network-manager-openvpn (Fedora) => plasma-nm
** Changed in: plasma-nm
Importance: Undecided => Unknown
** Changed in: plasma-nm
Status: New => Unknown
** Changed in: plasma-nm
Remote watch: None => KDE Bug Tracking System #349282
--
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:
Unknown
Status in network-manager-openvpn package in Ubuntu:
Confirmed
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
** Tags removed: network-manager openvpn
** Tags added: xenial
--
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:
Unknown
Status in network-manager-openvpn package in Ubuntu:
Confirmed
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
The error I get is:
"The file 'file.ovpn' could not be read or does not contain recognized
VPN connection information
Error: Key file contains line 'dev tun' which is not a key-value pair,
group, or comment."
If I edit the file and remove the line "comp-lzo adaptive" from the end
of the file the import is successful.
--
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 network-manager-openvpn package in Ubuntu:
Confirmed
Status in network-manager-openvpn package in Fedora:
New
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
I was able to import my config after making the adjustment outlined here
: https://askubuntu.com/a/816140
However now I am having issues with systemd and my tap device, I'm not
sure it's correctly creating it as I'm doing bridging not tunneling on
the server end :( (probably unrelated here though)
Also, please note that the above method for the import did not correctly
import my key direction, I had to change that after importing, which is
weird.
--
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 network-manager-openvpn package in Ubuntu:
Confirmed
Status in network-manager-openvpn package in Fedora:
New
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
im on 16.04.2 too, but i still see the bug. the workaround #77 didnt
help for me too..
--
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 network-manager-openvpn package in Ubuntu:
Confirmed
Status in network-manager-openvpn package in Fedora:
New
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
funnily enough, the bug is actually fixed, all what is needed is
actually network-manager-openvpn-gnome (I tested it on version
1.1.93-1ubuntu1.1 in 16.04.2) installed and then the network settings
configuration gui restarted so the new VPN shows up as openvpn, after
that importing the configuration from ovpn file works..
--
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 network-manager-openvpn package in Ubuntu:
Confirmed
Status in network-manager-openvpn package in Fedora:
New
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
** Also affects: network-manager-openvpn (Fedora)
Importance: Undecided
Status: New
--
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 network-manager-openvpn package in Ubuntu:
Confirmed
Status in network-manager-openvpn package in Fedora:
New
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
I'm on ubuntu 16.10,
I have pfsense running my openVPN service, and I exported the client
config to an ovpn file (inline).
When I get network-manager to import, I STILL get "the plugin does not
support import capability".
This bug has been open for OVER 6 YEARS now. How about we get this
conclusively fixed already??? I have to switch to Windows to VPN in, I
can't get network-manager to use any of my VPN info, even if I manually
enter it.
It's mind-blowing this still exists as a problem.
--
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 network-manager-openvpn package in Ubuntu:
Confirmed
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
This is working for me now. When I import into Network Manager, it
literally tells me which line is the problem now, and whatever line that
is, I comment it out and it works. Before, it would just tell me that
there was an issue importing but it wasn't specific. But at least now,
Network Manager helps me figure out the issue. I recently switched to
Ubuntu GNOME, so I'm not sure if there's something specific with the
GNOME implementation that displays specific errors, or if Network
Manager has changed. At least it's working for me now, albeit with
manual intervention being required.
In my opinion, the real issue at this point is that even though
commenting out some lines helps, each line is valid and should be
accepted. If I export an .ovpn file and use it via the command line, it
works without issue (even without commenting out anything). In my view,
if the config file is valid enough for OpenVPN itself, it should surely
be valid for Network Manager. Perhaps the OpenVPN spec has updated and
Network Manager hasn't been updated to match?
--
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 network-manager-openvpn package in Ubuntu:
Confirmed
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
I'm sorry, but im a newbie, but how does this fix get into the ubuntu
versions? Do we have to wait until network-manager-openvpn (Ubuntu) gets
assigned?
--
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 network-manager-openvpn package in Ubuntu:
Confirmed
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
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
I've found that removing the #comments in the TA key helped.
--
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 network-manager-openvpn package in Ubuntu:
Confirmed
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
