[Bug 163212] Re: network-manager-openvpn (kubuntu knetworkmanager version) with password authentication not working
BenH
ben at hewson-venieri.com
Sat Dec 1 10:45:24 UTC 2007
I have a similar problem where under Gnome(gusty) I have a VPN
connection setup using X509 key and a password. This works fine in Gnome
, but when I try in KDE it just won't connect. Knetwork-manager does not
ask for the password.
This is similar to bug #132060 however I have no problems using VPN and
Gnome.
>From syslog I have the following
Under Gnome.
Dec 1 10:10:42 desktop NetworkManager: <info> Will activate VPN connection 'Work1(firewall1)', service 'org.freedesktop.NetworkManager.openvpn', user_name 'ben', vpn_data 'connection-type / x509 / dev / tun / remote / ***.***.***.*** / port / 1194 / proto / udp / servercert-insecure / no / ca / /home/ben/vpn/client.pem / cert / home/ben/vpn/client.crt / key / /home/ben/vpn/client.key / comp-lzo / yes / shared-key / / local-ip / / remote-ip / / username / ', route '192.168.0.0/16'.
Under KDE
Dec 1 10:07:44 desktop NetworkManager: <info> Will activate VPN connection 'Work1(firewall1)', service 'org.freedesktop.NetworkManager.openvpn', user_name 'ben', vpn_data 'connection-type / x509 / remote / ***.***.***.*** / port / 1194 / ca / /home/ben/vpn/client.pem / cert / /home/ben/vpn/client.crt / key / /home/ben/vpn/client.key / comp-lzo / yes / shared-key / / username / / local-ip / / remote-ip / / dev / tun / proto / udp / ta-dir / none', route '192.168.0.0/16'.
:
:
:
Dec 1 10:07:44 desktop nm-openvpn[6894]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Dec 1 10:07:59 desktop nm-openvpn[6894]: ERROR: could not read Private Key username/password from management interface
There is a slight difference, Gnome has "servercert-insecure" and KDE
does not.
--
network-manager-openvpn (kubuntu knetworkmanager version) with password authentication not working
https://bugs.launchpad.net/bugs/163212
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for knetworkmanager in ubuntu.
More information about the kubuntu-bugs
mailing list