[ale] Still using plain FTP? Why?

Ken Cochran kwc at shell.TheWorld.com
Tue Jan 20 09:45:16 EST 2015


Q:  With rsync, how do I *not* encrypt the sync/transfer?

Say, I want to speed up an rsync run & don't need/care to
encrypt the syn/transfer (at least not "over the wire" -
file(s) may already be encrypted and/or compressed) but *do*
want to protect the sign-on.  Same for compression, e.g. I
want to turn *off* compression for already-compressed files.

Where in the FM do I RT?  :)  Thanks, -kc

> Date: Tue, 20 Jan 2015 08:18:06 -0500
> From: JD <jdp at algoloma.com>
> To: Atlanta Linux Enthusiasts <ale at ale.org>
> Subject: Re: [ale] Still using plain FTP? Why?
>
> On 01/20/2015 08:01 AM, Raj Wurttemberg wrote:
> > My biggest battle lately is transferring many (4,000+) large (100+GB) files
> > and needing to do parallel transfers to fully utilize the (internal) pipe. At
> > the moment, we are transferring the data from a 3TB HD (USB3) over 1G
> > ethernet.  I'm using rsync to copy the files. Security or encryption is not
> > needed (the files are actually encrypted) because all of the file transfers
> > are on the internal LAN (there is no Internet access).
> >
>
> rsync uses ssh to do network transfers by default (for the last
> 8 yrs at least), so you might be encrypting without meaning to.
>
> rsync manpage:
> "Typically, rsync is configured to use ssh by
>  default, but you may prefer to use rsh on a local network."


More information about the Ale mailing list