2010/2/9 Dr. David Kirkby <david.kir...@onetel.net>:
> I can sort of understand that, though I would have expected the restriction
> to only apply to the $HOME/.ssh directory, which should not even be readable
> by your group.
I stumbled into this trap at a previous time and it took me several hours and
debugging. The problem is that even an "ssh -v u...@host" don't tells you
why the authentication falls back to password. I assume there is a
configuration
option to change this behaviour which does not sound logical to me.
> But as I pointed out, a user can't ssh to his own account without taking
> steps to do so - at least on Solaris.
I took the relevant steps:
ssh-copy-id sameu...@localhost
(or doing this step manually) does the trick.
> One has to copy ones own public key to $HOME/.ssh/authorized_keys.
Yes. As always if any user wants password less login.
> I can't answer that for you. I would suggest you post that as a separate
> question, as you are more likely to get an answer that way, though perhaps
> someone reading this will know.
Sure. I'll do so.
Kind regards
Andreas.
--
http://fam-tille.de
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org
