Date: Wed, 11 Nov 2015 16:27:08 +0800 From: Ben Woods <woodsb02@gmail.com> To: John-Mark Gurney <jmg@funkthat.com> Cc: Bryan Drewery <bdrewery@freebsd.org>, =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= <des@des.no>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, "freebsd-security@freebsd.org" <freebsd-security@freebsd.org> Subject: Re: OpenSSH HPN Message-ID: <CAOc73CD4Hx_Jkmyg0F9Hx=KzytdrP6e7Bg9Y-FsLMiu32LLfFA@mail.gmail.com> In-Reply-To: <20151111075930.GR65715@funkthat.com> References: <86io5a9ome.fsf@desk.des.no> <20151110175216.GN65715@funkthat.com> <56428C84.8050600@FreeBSD.org> <CAOc73CAHQ0FRPES7GrM6ckkWfgZCS3Se7GFUrDO4pR_EMVSvZQ@mail.gmail.com> <20151111075930.GR65715@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, 11 November 2015, John-Mark Gurney <jmg@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. -- -- From: Benjamin Woods woodsb02@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOc73CD4Hx_Jkmyg0F9Hx=KzytdrP6e7Bg9Y-FsLMiu32LLfFA>