Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 22 Sep 2005 14:28:11 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: OpenSSH_4.2p1 and scp Message-ID: <20050922122811.GL12256@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Sep 22 08:12, Robert Watkins wrote: > Noticed something odd with OpenSSH_4.2p1 and scp. > > I can ssh to a Sun box (using Sun_SSH_1.0.1) without difficulties; the > problem arises when I try a file transfer with scp. The transfer starts > okay but exits almost immediately: > > ... > debug1: Entering interactive session. > debug1: Sending command: scp -v -f archive.tar.gz > Sending file modes: C0644 4585668 archive.tar.gz > Sink: C0644 4585668 archive.tar.gz > archive.tar.gz 3% 136KB 64.8KB/s 01:07 ETA > debug1: channel 0: free: client-session, nchannels 1 > Connection to remote.host.com closed by remote host. > debug1: Transferred: stdin 0, stdout 0, stderr 63 bytes in 3.1 seconds > debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 20.4 > debug1: Exit status -1 > > Reverting back to OpenSSH_4.1p1 fixed the problem. > > Any thoughts? SSH 4.2 might be more sensitive when it comes to output in a .profile (or .cshrc, .zshrc, etc) file. Keep in mind that the session is interactive when scp is used. Check your profile and make sure that nothing gets printed when running it. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/