Re: GatewayPorts does not open remote end
From: Jan Engelhardt (jengelh_at_linux01.gwdg.de)
Date: 01/22/05
- Next message: Darren Tucker: "Re: GatewayPorts does not open remote end"
- Previous message: Darren Tucker: "Re: openssh upgrade breaks login"
- In reply to: Darren Tucker: "Re: GatewayPorts does not open remote end"
- Next in thread: Darren Tucker: "Re: GatewayPorts does not open remote end"
- Reply: Darren Tucker: "Re: GatewayPorts does not open remote end"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 22 Jan 2005 10:54:15 +0100
>>ssh -o GatewayPorts=yes -L 12345:localhost:22 -R 23456:localhost:22
>>user@external
>>
>>only binds internal:12345 to the wildcard address, external:23456 is still
>>bound to 127.0.0.1 only. Is there a way I can also bind 23456 to the wildcard
>>address?
(Using openssh-3.5p1-117/Linux on the server side)
>Make sure it's permitted by the server. On OpenSSH this is the
>GatewayPorts option in sshd_config, and it defaults to "no". Other
>implementations may vary.
But if the sshd_config (which I may not edit, for I am not root) has
GatewayPorts = yes, then all -L and -R would be forwarded, even for users
which do not want Gatewayports.
Jan Engelhardt
-- If you knew the language, you'd know that: 私は考える、従って私はある。
- Next message: Darren Tucker: "Re: GatewayPorts does not open remote end"
- Previous message: Darren Tucker: "Re: openssh upgrade breaks login"
- In reply to: Darren Tucker: "Re: GatewayPorts does not open remote end"
- Next in thread: Darren Tucker: "Re: GatewayPorts does not open remote end"
- Reply: Darren Tucker: "Re: GatewayPorts does not open remote end"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]