Bug 180275

Summary: scp fails with no error message when the target machine calls stdout
Product: Red Hat Enterprise Linux 3 Reporter: Bob O'Conner <oconner>
Component: opensshAssignee: Tomas Mraz <tmraz>
Status: CLOSED NOTABUG QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-06 22:27:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.