Cisco vpnclient Bug (Cannot secure command line arguments)
Who is stupid? Me or the Cisco vpnclient for Linux? WTF...
I got this error message several times in the past, but did always work around
it by using Citrix Web Access instead of the VPN tunnel to connect to my
company. Once I tried to track it down using strace and some other magic,
but I didn't succeed, so I gave it up.
One hour ago, I was at the CCV
and used the vpnclient since 8am in the morning and it did work all the time.
Now that I'm at home, it complains with this error message. Needless to say,
I didn't change anything on the configuration of my laptop.
It seems to have something todo with the user's (root's) environment and
therefore I tried to work around this problem by using sudo. And well, it
works, but can anybody please explain the difference to me?
tuxxpad:~# vpnclient connect Landeskrankenhaus_Villach
fdopen: Invalid argument
Cannot secure command line arguments.
tuxxpad:~# sudo vpnclient connect Landeskrankenhaus_Villach
Cisco Systems VPN Client Version 4.7.00 (0640)
Copyright (C) 1998-2005 Cisco Systems, Inc. All Rights Reserved.
Client Type(s): Linux
Running on: Linux 126.96.36.199 #13 Mon May 29 14:59:30 CEST 2006 i686
Config file directory: /etc/opt/cisco-vpnclient
Initializing the VPN connection.
What is the difference in using sudo when I'm already root?