Unfortunately, this bypasses your .bash_profile, so if you have ssh-agent/keychain setup if doesn't do the authentication properly. bummer.

[ Reply to This | # ]

You should probably upgrade from the CLI-based ssh-agent to the SSHKeychain.app. It works great for me.

---
http://spacebit.dyndns.org

[ Reply to This | # ]

I don't use ssh with the keychain at all, just the standard id_rsa stuff, and that works fine for me. This is sweet. :) ssh bookmark + quicksilver's safari plugin = easy remote shell access.

[ Reply to This | # ]

That means that your private key is not password protected. So should someone break into your machine, they can easily login to any account you've copied your public key to. Even worse, they can look at your .ssh/known_hosts file to find a convenient list of all those accounts.

You really should passphrase protect your private key and then use ssh-agent. You'll have the same level of convenience, but quite a bit more security. And it's easy with the application mentioned in the previous comment (though personally, I've rolled my own solution and that's posted here as well as a series of three hints.)

[ Reply to This | # ]

Try using .profile instead.

[ Reply to This | # ]

Does anyone know if there's a way to pass arguments to ssh via this method? For example, if I want to do port forwarding.

---
Jayson --When Microsoft asks you, "Where do you want to go today?" tell them "Apple."

[ Reply to This | # ]

You could just use the Terminal's "Connect to Server", which will let you setup servers as well as specify custom options for ssh. Then just command+shift+k, pick a server from list, connect. Sure, safari bookmark beats it (especially when you sync your bookmarks between machines), but the terminal's way gives you much more power.

[ Reply to This | # ]

Assuming you always use the same port-forwarding (or at least, a common set), you could setup the port-forwarding in your .ssh/config file. If you have different sets of forwards you like to use, just add multiple configs. e.g.:

Host foo
   HostName realhostname.domain.com
   LocalForward 1234:127.0.0.1:5678
   LocalForward 5678:1.2.3.4:5678
Host bar
   Hostname realhostname.domain.com
   LocalForward 8000:127.0.0.1:80

Then if you ssh://foo it will connect you to realhostname.domain.com with the first set of forwards. If you ss://bar, it'll get you to the second set. etc.

[ Reply to This | # ]

Anyone know if it is possible to change the default terminal client to be something different? For example iterm.

[ Reply to This | # ]

If you install the RCDefaultApp preference pane, you can set the ssh URL to open iTerm.app instead of Terminal.app. The only problem is that iTerm doesn't appear to then handle the URL that's been passed to it (I'm actually not sure how Safari passes the URL along to Terminal.app either...).

So we're halfway there. To make things work with iTerm, you might want to submit an enhancement request to the author. Unfortunately I don't have time to take a look at it any more right now. Sorry. :-(

[ Reply to This | # ]

ssh actually handles the URL so from the command line you can

 ssh user@host 

Which is the same as.

 ssh -l user host 

[ Reply to This | # ]

Cool tip! Fast and Easy.

(JellyfiSSH still has some advantages, with regular ssh bookmarks and bookmarks for ssh tunnels)

[ Reply to This | # ]