News for hackers. Stuff that matters.
Re:Why is ssh insecure by default? [AllowTcpForwarding] by wmf on Saturday August 08, 2009 @06:15PM (#749907)
Maybe you didn't read carefully enough. Users who don't have shell access probably should not be able to proxy traffic through the server, but OpenSSH allows it by default.
Re:Why is ssh insecure by default? [AllowTcpForwarding] by skorgu on Sunday August 09, 2009 @01:33AM (#750390)
Being flippant for a minute, if you want your users to have access to a box but not have a shell, a tool called "secure shell" may not be the wisest choice.

Setting the default to frankly crippling levels for the primary function of a tool to accommodate an edge case seems slightly backwards to me. Host firewalls and/or disabling the option seem to be an acceptable set of hardening tasks if that use case is relevant to you.

Re:Why is ssh insecure by default? [AllowTcpForwarding] by thras on Saturday August 08, 2009 @07:18PM (#749980)
But you have to set that sort of user account up specially, at which time you can disable tcp forwarding. What he wants to change is the sshd default.
Re:Why is ssh insecure by default? [AllowTcpForwarding] by lallysingh on Saturday August 08, 2009 @11:21PM (#750277)
I agree with the poster.

There are two situations:

1) Nonshell use only -- you want port forwarding turned off. Unless you're using the machine as a proxy, it's just waiting to be used as part of a larger hack scheme.

2) Shell use only -- Normal logging in and shell use doesn't necessitate port forwarding. The only time it is generally useful is for forwarding X11 back to the client, but frankly that's not nearly as useful as it was 10 years ago. If you've got an X install on your server, and an X server on your client, then you're in a sufficiently-select subset of the user population to have to turn on one config option in sshd_config.

In either case, I think it should be turned off by default.