Terminal: Making SSH Protocol 2 default.

Is there any solution to this? I'm having the same problem, and is annoying. The default should be "automatic", not protocol 1.

Check it out...

http://developer.apple.com/mac/library/documentation/Darwin/Reference/ManPages/m an1/ssh.1.html

Sorry, wasn't specific on my previous response. I meant the default from the "New Remote Connection" dialog (not commandline, which already uses either ~/.ssh/config or /etc/ssh_config).
The dialog box doesn't take the settings, specifically Protocol, from the config file.

Is there some plist file somewhere that configures that dialog?

This is actually a serious security problem.

SSH1 is often wisely not supported by target hosts but if left on and this default left to stand, the user is connecting on a less secure means than they used to assume.

Yes, the New Remote Connection thing now defaults to SSH Protocol 1, the version you do NOT want to use by default. Automatic is the right choice, and used to be the default. The Terminal New Remote Connection window was altered in Snow Leopard to have this new behavior and it's both a BAD IDEA and an annoyance.

Like others on this thread, we in my company use terminal quite heavily for opening windows to servers all day. We all noticed this change within minutes of finishing the upgrade to Snow Leopard. While there's lots of great things about Snow Leopard, we were disappointed with this fault.

Workaround:

When adding a new remove connection, specify the "-2" option. For example, if you're connecting to "host1.example.org," click the icon to add a new remote connection, then put "host1.example.org -2" in the box. In the connection command box at the bottom of the New Remote Connection screen, the command will say "ssh -1 user@host1.example.org -2".

When you specify -2 after -1 in the SSH command, the -2 takes precedence. I tested this with a server I know only accepts protocol 2. When I connect without the -2, I get the error "Protocol major versions differ: 1 vs. 2." When I add the -2 to the server name, it lets me log in.

It's obviously not a great fix, because a great fix would be for Apple to correct what is obviously a serious security bug. However, it's an okay workaround that gets rid of the annoyance.

Great work around. Thanks. You're right, Apple fixing it would be best, but this does get rid of the annoyance.

for what it's worth, I filed a bug with the developer site on this. I suspect is may have been reported. I'll let you know if it gets marked duplicate or not.

Thanks. Please do post with any information. It is very annoying when security holes are added to perfectly good software.