Login Main site Create account

30.05.2006 20:13

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 #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?
Comments added earlier to http://tuxx-home.at/archives/2006/05/30/T20_13_31/index.html:
randy on 2006-10-05 18:43:55 wrote:
I have this same problem, although I haven't installed Sudo on the machine yet. To tell the different between the 2 environments, do something like

$ env > root.env
$ sudo env >sudo.env

diff root.env sudo.env
Alexander Griesser on 2006-10-14 11:20:42 wrote:
Well, there is no real difference in the environment, except
for some missing environment variables like HZ, PS1, PWD and
SHLVL, but they shouldn't be important for the proper function
of the Cisco VPN Client.

And if they are, Cisco's VPN Client is definetly more broken
than I ever thought it is.

There must be another reason, why sudo helps in this case,
but as my time at the moment is very limited, I don't want to
find that out ;)
Guest on 2007-06-18 21:56:05 wrote:
Here's a data point for you:

So, I mounted the C$ share of my Windows desktop on my Fesity laptop via smbfs in order to pull over my profile file (.pcf)

And, because I'm clearly not awake, and intending to mount it on /mnt, I actually mounted it on /tmp

And vpnclient gave me "Unable to secure command line arguments". This was running from a root shell, though sudo didn't help, either.

Unmounting the fs from /tmp and all was well again.

Now, I'm an administrator on the Windows box, so /tmp should still have been writable, but obviously it wouldn't have been very unixy...

Alexander Griesser on 2008-01-03 09:49:15 wrote:
Please let's discuss all these issues in the newly created forum:


This comment system is not suitable for debugging such stuff.

Your comment (HTML tags will be stripped !!):

To verify You are not a bot, type down text from this image.

Your try: