From owner-freebsd-current@freebsd.org  Wed Nov 11 13:06:46 2015
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id C40F0A2C151
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Wed, 11 Nov 2015 13:06:46 +0000 (UTC) (envelope-from crest@rlwinm.de)
Received: from smtp.rlwinm.de (smtp.rlwinm.de [IPv6:2a01:4f8:201:31ef::e])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8947514F4
 for <freebsd-current@freebsd.org>; Wed, 11 Nov 2015 13:06:46 +0000 (UTC)
 (envelope-from crest@rlwinm.de)
Received: from crest.local (unknown [87.253.189.132])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by smtp.rlwinm.de (Postfix) with ESMTPSA id AE9626828
 for <freebsd-current@freebsd.org>; Wed, 11 Nov 2015 14:06:44 +0100 (CET)
Subject: Re: OpenSSH HPN
To: freebsd-current@freebsd.org
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>
From: Jan Bramkamp <crest@rlwinm.de>
Message-ID: <56433D64.2060409@rlwinm.de>
Date: Wed, 11 Nov 2015 14:06:44 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0)
 Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <CAOc73CD4Hx_Jkmyg0F9Hx=KzytdrP6e7Bg9Y-FsLMiu32LLfFA@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2015 13:06:46 -0000

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).