From owner-freebsd-security Wed Aug 23 13:16:51 2000 Delivered-To: freebsd-security@freebsd.org Received: from mindcrime.bit0.com (mindcrime.bit0.com [208.6.169.69]) by hub.freebsd.org (Postfix) with ESMTP id C297037B423 for ; Wed, 23 Aug 2000 13:16:43 -0700 (PDT) Received: from localhost (mandrews@localhost) by mindcrime.bit0.com (8.9.3/8.9.3) with ESMTP id QAA71709; Wed, 23 Aug 2000 16:15:38 -0400 (EDT) (envelope-from mandrews@bit0.com) Date: Wed, 23 Aug 2000 16:15:38 -0400 (EDT) From: Mike Andrews To: cjclark@alum.mit.edu Cc: freebsd-security@FreeBSD.ORG Subject: Re: scp and >2GB files In-Reply-To: <20000822231556.J28027@149.211.6.64.reflexcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 22 Aug 2000, Crist J . Clark wrote: > On Wed, Aug 23, 2000 at 01:36:46AM -0400, Mike Andrews wrote: > > Any plans to improve scp so it can copy files larger than 2^31 bytes? For > > those that haven't tried it, scp dies with "lost connection" almost > > immediately after authenticating. (I'm guessing it's seeing the file size > > as a negative number and getting confused.) > > > > It would make a disk-to-disk backup solution I'm working on much easier. > > With scp not able to do this easily, I'm not sure what I can use as a > > quick replacement - maybe dump/restore to stdout run over an ssh pipeline, > > or maybe rdist. I've run tar over an ssh pipeline, but tar doesn't like > > files over 2^31 bytes either... > > > > This is OpenSSH on 4.1-RELEASE, btw. > > Isn't, > > $ scp file1 remote:file2 > > Same as, > > $ ssh remote 'cat > file2' < file1 Yeah, that works of course, as did Scot's pipe variation... Why is it the incredibly obvious solutions never occur to me until after I post to a mailing list and make myself look really stupid? Thanks, though. :) Mike Andrews (MA12) * mandrews@dcr.net * http://www.bit0.com/ www.fark.com: If it's not news, it's Fark. (Or something like that.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message