Implicit SSL FTP Clients with Scripting? 43
malcomvetter asks: "I need a command line FTP client that supports 'Implicit SSL', sports some kind of scripting interface, and runs on Win32. Any suggestions? So far, I have only found GUI versions such as FileZilla."
I remember once needing a scripting FTP client long ago. It took me a long time, but I finally found one that had a workable but unintuitive interface. Have scripting FTP clients become more prevalent or is your best bet using something flexible with network bindings (like Python or Perl) to get the job done?
SCP? (Score:1)
Re:SCP? (Score:2)
Re:SCP? (Score:2)
By using key files, it's possible to create SCP sessions, which don't require passwords at all.
Re:SCP? (Score:3, Informative)
But privacy without entering a password is only one possible requirement. Another possible requirement is anonymity.
I assume that scp doesn't transmit the user's identity in cleartext (it shouldn't be necessary since the server has a public key), so anonymity over the wire presumably isn't an issue. But suppose I wanted to make sure that when the subpeona is issued, it would be trickier to associate a file transfer to a user. Then ft
scp (Score:2)
Re:scp (Score:3, Informative)
Problem is, pscp lacks large file support.
Re:scp (Score:3, Interesting)
plink username@hostname cat remote-filename > local-filename
For upload, use this instead:
plink username@hostname "cat > remote-filename" local-filename
Who needs a dedicated file transfer protocol?
(plink is the PuTTY package's equivalent of the standard command line SSH client, with no GUI nor terminal emulation)
Re:scp (Score:2)
plink username@hostname "cat > remote-filename" < local-filename
Re:scp (Score:2)
Re:scp (Score:1)
Oh man, that rocks. I didn't realize that existed (or maybe I never paid attention). I've been using WinSCP's slow-ass file transfer (and it is sloooooooow). Thanks!
try CoreFTP (Score:2)
cURL? (Score:5, Interesting)
If Cygwin is an option then lftp is perfect. (Score:3, Informative)
Re:If Cygwin is an option then lftp is perfect. (Score:2)
+1 to parent. We recommend lftp for use with our backup service [rimuhosting.com] (link includes commands for enabling/disabling tls support) since it supports all the goodies like tls, scripting, and mirroring in both directions.
--
Linux VPS Hosting [rimuhosting.com]
Re:WinSCP (Score:1)
Personally (Score:3, Interesting)
Cygwin (Score:2, Interesting)
Re:Cygwin (Score:1)
I have used it (and the command line versions of scp and ssh) for years.
Re:Cygwin (Score:1)
Re:Cygwin (Score:2)
Note this is cumbersome and suckky but I've been forced through similar hoops before and it's just one ugly hack in the bag of tricks.
Try Fugu for OSX (Score:3, Informative)
sftp (part of cygwin) (Score:2)
Re:sftp (part of cygwin) (Score:2, Informative)
Re:sftp (part of cygwin) (Score:2)
Actually that isn't 100% correct either IIRC. You must be able to run the scp binary on the server in addition to your client, so an admin could disable it by taking away execute permission on the server.
scp (Score:4, Interesting)
Expect (Score:2, Informative)
A different approach (Score:1)
Why SSL instead of something related to SSH? (Score:2)
You just encrypt the passwords but not the data, if IIRC. Maybe think about something using the SSH protocol.
On Windows, the easiest solution/least expensive solution is probaby via Cygwin [cygwin.com] as another poster stated using SFTP from OpenSSH. If you need commercial software, I'd strongly recommed SecureFX [vandyke.com]from Van Dyke Software. Scriptable interface, supports FTP, SFTP and FTP over SSL. From the command line, I believe it doesn't support FTP over SSL but I could be wrong.
Re:Why SSL instead of something related to SSH? (Score:1)
FTP is also good for its various features you just cant do with SFTP/SCP, like site to site transfers, and scripting. For example, uploading a
expect is great for this (Score:5, Informative)
Some cool things, autoexpect, this will basically record a session you do (like the script command), and right an expect script for it. Also if you use the -p (I think, check the man) option, it won't make the prompts strict, just in case there is a datestamp in there.
4NT (Score:1, Interesting)
SecureFX (Score:3, Informative)
What about SSH certs and Rsync? (Score:5, Interesting)
SSH is configured to only allow transfers with a valid certificate from a valid IP address. There is no pass-phrase on the certs.
Copying / syncing directories is a breeze:
rsync -ae ssh server1:/copy/this/directory/
No fuss. I have not tried rsync on win32, but I am sure it exists. I do a lot of web development, but have not used a ftp client on a regular basis in years. My sites are backed up to remote servers using this method, and new sites are uploaded using rsync as well.
Its fast, easy to use and saves on bandwidth, as only changes are transfered. With FTP the whole file is always moved. SO bandwidth savings alone may be worth looking into this solution.
-MS2k
FTPRush (Score:1)
It has a full scriptable interface including some example mirc script to control it.
Just don't be lame and autotrade.
Google will find it, its too late to dig out links.
PSFTP (Score:2)
Re:PSFTP (Score:2)
Whereas the OP said: "I need a command line FTP client that supports 'Implicit SSL'"
SSH is not SSL.
Re:PSFTP (Score:2)
And maybe I'm a Chinese jet pilot.
FTP/TLS: All the goodies (Score:2)
Pretty much all you could need to know about FTP/TLS (TLS being the current Right Way to refer to SSL) is at the RFC author's "FTP/TLS State of Play" page [ford-hutchinson.com].
It covers things like the difference between SFTP (SSH) and FTPS (SSL) (although instead of discussing the merits of either, it links to another page)