Bug 109161 - ssh warns about sockopts not working when using ProxyCommand
ssh warns about sockopts not working when using ProxyCommand
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: openssh (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-11-05 03:58 EST by David Woodhouse
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-05-12 00:23:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:114 normal SHIPPED_LIVE Updated openssh packages fix password expiration bugs 2004-05-12 00:00:00 EDT

  None (edit)
Description David Woodhouse 2003-11-05 03:58:24 EST
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 3128'" pentafluge.infradead.org exec
getsockopt TCP_NODELAY: Socket operation on non-socket
* PREAUTH Ready.

Fix in $URL.
Comment 1 David Woodhouse 2003-11-05 03:59:43 EST
Bug also exists in FC1.
Comment 2 David Woodhouse 2003-11-06 07:06:18 EST
Will commit fix to package cvs tree later today unless I hear otherwise.
Comment 3 John Flanagan 2004-05-12 00:23:37 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.