Bug 173 - sshd does not listen on tcp-socket, though GatewayPorts yes
Summary: sshd does not listen on tcp-socket, though GatewayPorts yes
Status: CLOSED INVALID
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: sshd (show other bugs)
Version: -current
Hardware: UltraSPARC SunOS
: P2 normal
Assignee: OpenSSH Bugzilla mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-19 04:48 AEDT by Albert Fluegel
Modified: 2004-04-14 12:24 AEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Albert Fluegel 2002-03-19 04:48:59 AEDT
The summary says it all. The Changes file says:
 - (stevesk) OpenBSD CVS sync X11 localhost display
   - stevesk@cvs.openbsd.org 2001/11/29 14:10:51
     [channels.h channels.c session.c]
     sshd X11 fake server will now listen on localhost by default:
     $ echo $DISPLAY
     localhost:12.0
     $ netstat -an|grep 6012
     tcp        0      0  127.0.0.1.6012         *.*                    LISTEN
     tcp6       0      0  ::1.6012               *.*                    LISTEN
     sshd_config gatewayports=yes can be used to revert back to the old
     behavior.  will control this with another option later.  ok markus@

but that's not true. I have configured
GatewayPorts yes
and
X11Forwarding yes

but:
prompt# echo $DISPLAY
localhost:10.0
prompt# netstat -an|grep 6010
127.0.0.1.6010             *.*                0      0     0      0 LISTEN

WHY MUST EVERYTHING CONSTANTLY CHANGE ?
ESPECIALLY THE WORKING THINGS ?
Comment 1 Kevin Steves 2002-03-19 08:31:40 AEDT
see sshd.8 X11UseLocalhost
Comment 2 Markus Friedl 2002-03-20 07:47:57 AEDT
no openssh release had GatewayPorts affect X11-forwarding.

the X11 sockets are now bound to localhost for security
reasons, if you don't like this, please check the
annoucement or sshd(8)
Comment 3 Kevin Steves 2002-03-31 04:09:19 AEST
closing.
Comment 4 Damien Miller 2004-04-14 12:24:18 AEST
Mass change of RESOLVED bugs to CLOSED