SSH connection with private key and port 222

ssh -i /root/.ssh/username\@hostname -p 222 username@hostname

2011-09-30 11:23:22

What Others Think

The command is correct, however, there is nothing to win on having a different private/public keypair for every different hosts, like it looks like here. Having one for private, one at work, and one per script that cant use password is sufficient.
xeor · 394 weeks and 5 days ago
@xeor Nonsense. I've generated a public/private key pair, and uploaded both to every Amazon instance for work. This is for file transfer between each instance, and between my terminal and the instance. While this is great, there is no way in hell I'm going to reuse the exact same key for my client's blog that I use for backup via rsync. That would give my client the keys to my employer's kingdom (and the reverse too). . Think about keying every single room in a hotel to the exact same biting. Super convenient, and what could possibly go wrong?
unixmonkey8121 · 394 weeks and 4 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: