openssh bugs - May 2005 - [Bug 1037] Man page for -L and -R should mention -g

http://bugzilla.mindrot.org/show_bug.cgi?id=1037

           Summary: Man page for -L and -R should mention -g
           Product: Portable OpenSSH
           Version: 4.0p1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: trivial
          Priority: P5
         Component: Documentation
        AssignedTo: bitbucket at mindrot.org
        ReportedBy: bugzilla.mindrot.org at tange.dk


The manual page for -L and -R does not mention -g. Since the default behaviour 
has changed it would be nice if the sections on -L and -R ended with: See also 
-g to allow remote hosts to connect.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1037





------- Additional Comments From markus at openbsd.org  2005-05-12 19:56 -------
hm, how did the default change?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1037





------- Additional Comments From bugzilla.mindrot.org at tange.dk  2005-05-12
20:39 -------
Earlier it was the default that remote hosts could connect to a forwarded port. 
Now you will have to explicitly use -g. In any case it would be nice if -g was 
mentioned in relation to -L.  



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1037





------- Additional Comments From djm at mindrot.org  2005-05-12 20:51 -------
No, GatewayPorts=no has always been the default.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1037





------- Additional Comments From dtucker at zip.com.au  2005-05-12 21:59 -------
It's true that the default for GatewayPorts hasn't changed, but it will
now
affect the address_to_bind in remote port forwards where previously it
wouldn't
(the client always sent 0.0.0.0).

"ssh -R 1234:localhost:22 -v -N localhost" gives:
Remote connections from LOCALHOST:1234 forwarded to local address localhost:22

"ssh -R 1234:localhost:22 -g -v -N localhost" gives:
Remote connections from *:1234 forwarded to local address localhost:22

(In recent OpenSSH servers, this is further modified if GatewayPorts is
"clientspecified").



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1037





------- Additional Comments From djm at mindrot.org  2005-06-03 12:27 -------
Created an attachment (id=925)
 --> (http://bugzilla.mindrot.org/attachment.cgi?id=925&action=view)
Fix misleading log message

I don't think so: a client's GatewayPorts isn't propogated to the
server, nor
is it used to fill in the address_to_bind if none is specified. 

Note that the log message in ssh_init_forwarding() is incorrect (see
attachment) - it tells the user that the listen_address depends on
gateway_ports.

See channels.c:channel_request_remote_forwarding() - it always sends a
listen_addr of localhost if none is specified.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.