Bug 180275 - scp fails with no error message when the target machine calls stdout
Summary: scp fails with no error message when the target machine calls stdout
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: openssh
Version: 3.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Brian Brock
URL:
Whiteboard:
: 180276 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-06 21:12 UTC by Bob O'Conner
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-06 22:27:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Bob O'Conner 2006-02-06 21:12:43 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 2.0.50727)

Description of problem:


Version-Release number of selected component (if applicable):
openssh 3.6.1

How reproducible:
Always

Steps to Reproduce:
1. scp from RHE3 to RHE3, with an echo in the .bashrc
2.
3.
  

Actual Results:  scp returns, no error message, the file has failed to be copied.

Expected Results:  The file should have been copied 

Additional info:
Comment 1 Tomas Mraz 2006-02-06 22:26:35 UTC 
*** Bug 180276 has been marked as a duplicate of this bug. ***
Comment 2 Tomas Mraz 2006-02-06 22:27:58 UTC 
This is limitation of the scp protocol which can't be easily overcomed. Use sftp
or setup server to not echo anything in .bashrc.
Note You need to log in before you can comment on or make changes to this bug.