Date: Wed, 11 Nov 2015 14:06:44 +0100 From: Jan Bramkamp <crest@rlwinm.de> To: freebsd-current@freebsd.org Subject: Re: OpenSSH HPN Message-ID: <56433D64.2060409@rlwinm.de> In-Reply-To: <CAOc73CD4Hx_Jkmyg0F9Hx=KzytdrP6e7Bg9Y-FsLMiu32LLfFA@mail.gmail.com> References: <86io5a9ome.fsf@desk.des.no> <20151110175216.GN65715@funkthat.com> <56428C84.8050600@FreeBSD.org> <CAOc73CAHQ0FRPES7GrM6ckkWfgZCS3Se7GFUrDO4pR_EMVSvZQ@mail.gmail.com> <20151111075930.GR65715@funkthat.com> <CAOc73CD4Hx_Jkmyg0F9Hx=KzytdrP6e7Bg9Y-FsLMiu32LLfFA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/11/15 09:27, Ben Woods wrote: > 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. Sounds like you're looking for rsyncd instead of rsync over ssh (minus encryption).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56433D64.2060409>