[K12OSN] how to set up passwordless ssh access

[Krsnendu dasa]

I have passwordless access from K12LTSP at school to my ubuntu box at home.
No problem.
But I still can get passwordless access from home to school I have followed
all the advice given and it still doesn't work????
I have 2 k12ltsp servers in parallel, perhaps that has something to do with
it?

Anyway it is not essential.

It seems in the process I have broken my nx private key settings.  At
present I can NX log into the secondary K12LTSP server and can access my
/home directory, but I don't have root access to the file system on the main
box from there. I can't log in to the main server as root or as myself. It
says it is using public key authentication. This is the message that usually
comes if you try to connect without importing the private key. The key on
the client and the server seem to match.

What is the process for regenerating the keys? Any other suggestions for how
to fix this problem?

On 02/07/07, Micha Silver <micha at arava.co.il> wrote:
>
> Seth Hasani wrote:
>
> > On 6/15/07, Krsnendu dasa <krsnendu108 at gmail.com> wrote:
> >> I have run ssh-keygen on my home Ubuntu computer.
> >> Then I pasted the contents of id_rsa.pub into ~/.ssh/authorized_keys
> >> on the K12LTSP server.
> >>
> >> When I ssh in it still prompts me for my password.
> >
> > Makes sense because your client doesnt have the server's key but your
> > server surely does have the client's key. The client needs the
> > server's key to connect passwordless. (and all of that permissions
> > stuff given in this thread has to be in place as well.)
> >
> I believe this is incorrect. You never need to create a key pair on a
> server, only on the client computer that needs to connect to the server.
> >> What else do have have to do so I don't have to enter my password
> >> every time I ssh in?
> >
> 1- On your client computer create a key pair using: ssh-keygen -t dsa.
> Do *not* enter a passphrase.
> 2- Copy the contents of the file ~/.ssh/id_dsa.pub from your client
> computer (public half of the key) into the file ~/.ssh/authorized_keys
> on the server. You can do this easily with scp. Or open a second
> terminal and ssh (with password for now) into the server, then
> copy/paste from the local file to the server using the mouse.
> 3- Make sure permissions are correct. On the server
> ~.ssh/authorized_keys must be read only for the user, i.e. chmod 0600
> ~/.ssh/authorized_keys.
> That should do it.
>
> Regards,
> Micha
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Arava Development Co, Sapir, Israel
> tel: +972(8)-6592270
> cell: +972(52)-3665918
>
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/k12osn/attachments/20070706/5dec84ba/attachment.htm>