Ben Woods wrote this message on Wed, Nov 11, 2015 at 16:27 +0800:
> On Wednesday, 11 November 2015, John-Mark Gurney <j...@funkthat.com> wrote:
> > Ben Woods wrote this message on Wed, Nov 11, 2015 at 15:40 +0800:
> > > I have to agree that there are cases when the NONE cipher makes sense,
> > and
> > > it is up to the end user to make sure they know what they are doing.
> > >
> > > Personally I have used it at home to backup my old FreeBSD server (which
> > > does not have AESNI) over a dedicated network connection to a backup
> > server
> > > using rsync/ssh. Since it was not possible for anyone else to be on that
> > > local network, and the server was so old it didn't have AESNI and would
> > > soon be retired, using the NONE cipher sped up the transfer
> > significantly.
> > If you have a trusted network, why not just use nc?
> Honest answer: ignorance of how I can use netcat together with rsync.
A quick google of rsync nc, turned up method 2 & 4 from:
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"