Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 3 product line. The current stable release is 3.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 109161

Summary: ssh warns about sockopts not working when using ProxyCommand
Product: Red Hat Enterprise Linux 3 Reporter: David Woodhouse <dwmw2>
Component: opensshAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/misc.c.diff?r1=1.22&r2=1.23
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-05-12 04:23:37 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 David Woodhouse 2003-11-05 08:58:24 UTC 
When using a proxycommand, SSH always gives a warning about not being
able to set the TCP_NODELAY socket option on the pipe which it's using
to communicate with the proxycommand. This extra line of output
confuses many things which use SSH to invoke remote commands,
including pine...


$ ssh -o "proxycommand sh -c '( echo CONNECT %h:%p HTTP/1.0; echo; cat
) | nc 192.168.0.1 3128'" pentafluge.infradead.org exec
bin/courier-imap.sh
getsockopt TCP_NODELAY: Socket operation on non-socket
* PREAUTH Ready.

Fix in $URL.
Comment 1 David Woodhouse 2003-11-05 08:59:43 UTC 
Bug also exists in FC1.
Comment 2 David Woodhouse 2003-11-06 12:06:18 UTC 
Will commit fix to package cvs tree later today unless I hear otherwise.
Comment 3 John Flanagan 2004-05-12 04:23:37 UTC 
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2004-114.html