search for: gatewayport

http://bugzilla.mindrot.org/show_bug.cgi?id=760 Summary: GatewayPorts clarification in _config man pages Product: Portable OpenSSH Version: 3.7p1 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: Documentation AssignedTo: openssh-bugs at mindrot.o...

...eners on the <dest ip> with listener ip 127.0.0.1, ::1 and not 127.0.0.2 Adding the following code to channels.c after line 2660 } else if (host) { addr = listen_addr; results in having the sshd start the 127.0.0.2 listener. Maybe there has to be some check against the GatewayPorts option as well. -- Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

...mparing with a fresh install, here are the diffs : > > root:/etc# diff /etc/ssh/sshd_config /tmp/sshd_config > 43a44 > > LogLevel DEBUG3 > 48c49 > < #PermitRootLogin yes > --- > > PermitRootLogin yes > 114,115c115,116 > < #AllowTcpForwarding yes > < #GatewayPorts no > --- > > AllowTcpForwarding yes > > GatewayPorts yes > > The man page specifically says that the -R option won't work unless > GatewayPorts is set to yes, and it is NOT able by default. > But i don't remember if this was sufficient, because I may have > c...

http://bugzilla.mindrot.org/show_bug.cgi?id=173 Summary: sshd does not listen on tcp-socket, though GatewayPorts yes Product: Portable OpenSSH Version: 3.1p1 Platform: UltraSparc OS/Version: SunOS Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org...

https://bugzilla.mindrot.org/show_bug.cgi?id=2222 Bug ID: 2222 Summary: GatewayPorts=no should not rewrite localhost addresses in port-forward requests Product: Portable OpenSSH Version: 6.5p1 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 Component: sshd...

http://bugzilla.mindrot.org/show_bug.cgi?id=413 markus at openbsd.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From markus at openbsd.org 2003-02-03 19:50 ------- i'll look into this. ------- You are

...and the archive haven't helped. Thanks in advance for your time and consideration. -server- uname -a Linux example.com 2.6.18-128.7.1.el5xen #1 SMP Mon Aug 24 10:08:55 EDT 2009 i686 i686 i386 GNU/Linux OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008 -sshd_config- AllowTcpForwarding yes GatewayPorts yes -from other system- ssh -R 127.0.0.10:12491:127.0.0.1:5000 foo at example.com -messages- Aug 12 16:22:45 xxx sshd[1440]: debug1: server_input_global_request: tcpip-forward listen 127.0.0.10 port 12491 Aug 12 16:22:45 xxx sshd[1440]: debug1: Local forwarding listening on :: port 12491. Aug 12...

http://bugzilla.mindrot.org/show_bug.cgi?id=530 Summary: problems with port forwarding Product: Portable OpenSSH Version: 3.5p1 Platform: ix86 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: gilbert at

...|Added ---------------------------------------------------------------------------- Summary|Remote forwards do not bind |No feedback when remote |to the selected address |forward is localhost-only | |due to GatewayPorts Severity|normal |minor Priority|P2 |P3 ------- Comment #3 from ted at midg3t.net 2007-03-14 01:53 ------- That was bound to happen. Of course this behaviour is by design, I just didn't look hard enough. So now I'm req...

http://bugzilla.mindrot.org/show_bug.cgi?id=173 ------- Additional Comments From stevesk at pobox.com 2002-03-19 08:31 ------- see sshd.8 X11UseLocalhost ------- 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=203 Summary: X11 forwarding ignores GatewayPorts flag Product: Portable OpenSSH Version: 3.1p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: eric-openssh...

https://bugzilla.mindrot.org/show_bug.cgi?id=1297 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #6 from Damien Miller <djm at mindrot.org> --- Set all RESOLVED bugs to CLOSED with release

https://bugzilla.mindrot.org/show_bug.cgi?id=1297 --- Comment #4 from Damien Miller <djm at mindrot.org> 2008-06-12 18:18:50 --- Created an attachment (id=1515) --> (http://bugzilla.mindrot.org/attachment.cgi?id=1515) send notification in debug message Unfortunately there isn't any clean way for the server to inform the client - the best we can do is a debug message (see

http://bugzilla.mindrot.org/show_bug.cgi?id=203 ------- Additional Comments From dtucker at zip.com.au 2002-04-04 00:13 ------- Add "X11UseLocalhost no" to sshd_config on your server. More details can be found in the sshd man page. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

https://bugzilla.mindrot.org/show_bug.cgi?id=1297 Darren Tucker <dtucker at zip.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dtucker at zip.com.au Attachment #1515| |ok+ Flags|

I have the following line in the sshd_config file: GatewayPorts no If I launch the ssh client as this: ssh -l user host -R 9000:otherHost:25 the port forwarding is successful! :-( As you can see, the 'netstat -na' command shows the Secure Shell daemon listening to the port 9000. Active Internet connections (servers and established) Proto Recv...

...connect several devices to one master node in the mid. For this szenario we need some remote forwardings by ssh where each satellite node should establish a socket on another 127.0.0.0/8 address but each time the same port. Now it looks like we are going to be forced to 127.0.0.1 as long as we have GatewayPorts set to "no" by default. More explainations: client A is going to open a channel by: autossh -i privkey -R 127.0.0.2:2222:127.0.0.1:22 user at host client B is going to open a channel by: autossh -i privkey -R 127.0.0.3:2222:127.0.0.1:22 user at host client C is going to open a channel b...

http://bugzilla.mindrot.org/show_bug.cgi?id=413 ------- Additional Comments From dtucker at zip.com.au 2005-01-24 14:27 ------- Created an attachment (id=782) --> (http://bugzilla.mindrot.org/attachment.cgi?id=782&action=view) forward-bind.sh: regression test for binding port forwards to addresses Current limitations of test: - no testing of IPv6 - no testing of backwards compat

Hello, I just upgraded from 2.9p2 to 3.0.1p1 and good news. I don't have to patch channels.c to get Remote Port Forwarding to work. That is fantastic. It appears, however, that -g still doesn't work. I checked the archives and it doesn't look like anyone has mentioned it yet. What does work is if I ssh to a machine I can telnet to localhost on the forwarded port, but connecting to

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: