Thus spake Tim Kientzle <[EMAIL PROTECTED]>: > Thus spake Lucky Green <[EMAIL PROTECTED]>: > >>... remove ssh1 fallback from the default ... > > David Schultz <[EMAIL PROTECTED]> wrote: > >Removing SSH 1 ... is going to break compatibility ... > > > POLA: before breaking compatibility, warn people. > It's simple to modify the ssh client so that it > emits a warning message before downgrading > > "Warning: switching to less-secure SSH1 protocol" > > On the server side, you could certainly log > a warning; there may be a way to notify the > connecting user as well. The logged warning > could even include a very brief reference to > the setting required to disable SSH1 entirely.
I think you're missing the point. Warnings are fine, but there is little good reason to disable SSH1 entirely. If one end of the connection is forced to fall back to SSH1, it's almost certainly because the user at the other end _doesn't_have_any_other_option_. You're proposing to kick legitimate users off of everyone's FreeBSD boxen because you know better than they do about security. I know SSH1 is insecure, and therefore I don't use it. But I'm not about to unleash a surprise on everyone who uses a machine without SSH2 just so I can hammer the idea into their heads. Breaking POLA isn't a sin, but you'd better have a better reason to do it than ``it lets people do things that are insecure.'' So do rsh, telnet, hosts.equiv, vipw, et al. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message