Comments on: Beginning SSH on Ubuntu

By: Donny Bahama

Donny Bahama — Fri, 05 Feb 2010 06:31:45 +0000

A bit more info...

I had ssh'ed into cinemaloha when it was using DHCP. At that time, I was (successfully) using the name rather than the IP. When I saw this wonderful guide, I thought, "better give it a static IP before setting up the host entry." After doing so I was still able to ssh via the IP, but not by the hostname. I then setup the host entry per this guide, tried to ssh in, got the err msg above. Next I tried pinging cinemaloha. The pings were going to the old (DHCP) address (and of course, failing.) Is there some sort of local DNS cache?

By: Donny Bahama

Donny Bahama — Fri, 05 Feb 2010 06:19:54 +0000

Hmmm. Doesn't work for me. After entering the host info and trying "ssh cinemaloha" I get... "ssh: connect to host cinemaloha port 22: No route to host" :(

Any suggestions?

By: vishal

vishal — Sat, 19 Dec 2009 07:54:39 +0000

Nice article It’s Helpful for us

By: Gullele

Gullele — Wed, 09 Dec 2009 23:41:10 +0000

It is well written and nice one.

By: AOD

AOD — Sun, 15 Feb 2009 17:32:27 +0000

After much hunting through the web, wasting a lot of time plus a number of false starts, your tutorial for setting up an SSH client/server was the only one that got my system configured correctly. It's well written and follows a logical pattern - thanks very much.

Alan

ps fancy having a go at "howto" set up a chroot jail!!!!

By: Eats Wombats

Eats Wombats — Thu, 25 Sep 2008 10:07:23 +0000

Update:

My mistake was painfully simple: trying to SSH in the wrong direction, from the machine with the public key.

I’m not the only one to have done this so I posted a note to launchpad suggesting some clarification of the docs which are not at all clear on this (as well as on the authorized-keys filename). A diagram would help too.

I should say that the PubkeyAuthentication was already done and that no changes are needed to sshd_config at all.

This is helpful:

http://ubuntuforums.org/showthread.php?t=238672

By: Eats Wombats

Eats Wombats — Wed, 24 Sep 2008 14:01:35 +0000

You don't mention the need to have

PubkeyAuthentication yes

in sshd_config. I have done this but I'm not clear (yet) on what other things I should do at the same time, if any.

Loved the "Go forth and SSHify!"

By: Eats Wombats

Eats Wombats — Wed, 24 Sep 2008 13:51:46 +0000

Useful article. There’s a possible discrepancy with the info here

https://help.ubuntu.com/8.04/serverguide/C/openssh-server.html

you advise using authorized_keys, the Ubuntu site uses authorized_keys2.

I’m guessing that it depends on what’s in the sshd_config file, but the debian site (http://www.debian-administration.org/articles/152) is also a little confusing. I thought RSA was older but, not according to this.

I’m here because the Ubuntu page above isn’t working for me — trying to get passwordless authentication working. The first problem was I had forgotten I had a firewall rule blocking port 22 (smacks forehead!). It would be good in such docs if assumptions were enumerated with tests to verify applicability.

I think it’s particularly important for anything that will enable a new (to Ubuntu) user to set up a good backup regime. I’m looking to run rsync from my laptop over ssh.

Your docs are considerably better than the official ones! Thanks

By: john

john — Mon, 23 Jun 2008 14:35:07 +0000

try this -

web based ssh client, very useful when you’re behind a strict firewall.

http://www.browsershell.com

By: Brian

Brian — Sat, 07 Jun 2008 01:23:56 +0000

Nick, thanks for the kudos. I’m probably not qualified to comment directly on your setup. To connect to my SSH server from the WAN, I simply forward a port on my router’s config page, and link it to LAN IP of the Linux box running the server. Then, instead of typing ssh myaccount@192.168.xx.xx, I type ssh myaccount@my.WAN.IP, and the router takes care of the rest.