On Friday 08 Apr 2016 14:17:21 Neil Bothwick wrote: > On Fri, 8 Apr 2016 15:05:45 +0200, hw wrote: > > > However, the man page also advises against giving the password on the > > > command line (because it is then available to anyone with normal user > > > shell access while the command is running) and suggests using either > > > > I need to use it with a script for automatic downloads, so the password > > wouldn't appear in the history. Using a ~/.netrc would create a > > dependency on the user who runs the script, which is something I would > > prefer to avoid. > > It's not just the history, the password appears in the putput from ps > while the transfer is running. > > > > ~/.netrc, which you have already said works, or $LFTP_PASSWORD along > > > with --env-password. Have you tried this? > > > > > > LFTP_PASSWORD='pass(word' lftp --env-password -u user > > > ftp://example.com > > > > Thanks, that looks like a good solution. I'll see if that works ... > > If that doesn't work, you could always sidestep the issue by changing the > password to "password1" ;-)
I remember banging my head against a brick wall trying similar methods to get ssmtp to use a passwd with special characters. It would only accept alphanumeric characters. I wasn't sure if this was a bash or an ssmtp problem. I ended up changing the passwd. :-( -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
