After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 685788 - NM-OpenVPN - WARNING: No server certificate verification method has been enabled
NM-OpenVPN - WARNING: No server certificate verification method has been ena...
Status: RESOLVED DUPLICATE of bug 685790
Product: NetworkManager
Classification: Platform
Component: VPN: openvpn
0.9.x
Other Windows
: Normal critical
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-10-09 08:37 UTC by Das
Modified: 2012-10-09 10:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Das 2012-10-09 08:37:43 UTC
Hi Guys,

I'm running Slackware 14.0 x86 with Xfce 4.10 & OpenBox and these 
versions for NetworkManager;

NetworkManager-0.9.6.0
NetworkManager-openvpn-0.9.4.0

I noticed when looking through the logs for the NetworkManager when I'm 
running openvpn this message;

WARNING: No server certificate verification method has been enabled.

From what I can tell there is no way in which the config option;

ns-cert-type server

Can be used in NetworkManager, there appears to be no options to place 
this in to be used...

If I run openvpn from the command line I do not have this problem, 
here's output from the terminal;

Mon Oct  8 22:24:20 2012 OpenVPN 2.2.2 i486-slackware-linux-gnu [SSL] 
[LZO2] [EPOLL] [eurephia] built on Jul  4 2012
Mon Oct  8 22:24:20 2012 NOTE: OpenVPN 2.1 requires '--script-security 
2' or higher to call user-defined scripts or executables
Mon Oct  8 22:24:20 2012 Control Channel Authentication: using 
'/etc/openvpn/keys/ta.key' as a OpenVPN static key file
Mon Oct  8 22:24:20 2012 LZO compression initialized
Mon Oct  8 22:24:22 2012 UDPv4 link local: [undef]
Mon Oct  8 22:24:22 2012 UDPv4 link remote: 83.170.109.13:443
Mon Oct  8 22:24:39 2012 [server] Peer Connection Initiated with 
83.170.109.13:443
Mon Oct  8 22:24:43 2012 TUN/TAP device tun1 opened
Mon Oct  8 22:24:43 2012 /usr/sbin/ip link set dev tun1 up mtu 1500
Mon Oct  8 22:24:43 2012 /usr/sbin/ip addr add dev tun1 local 
172.16.1.18 peer 172.16.1.17
Mon Oct  8 22:24:46 2012 Initialization Sequence Completed

So how do we add in or use the ns-cert-type server option in the 
NetworkManager?

If there is no method at the moment this is really critical, as this can 
be a security issue with MITM attacks.

I hope I'll please get a reply back soon on this, this is a very 
critical security matter that needs resolving as soon as possible...

I'm attaching the Network Manager log...

THANKS
Comment 1 André Klapper 2012-10-09 10:01:59 UTC

*** This bug has been marked as a duplicate of bug 685790 ***