Okay, yes, setting SSH_AUTH_SOCK is the right thing to do, but this
strikes me as clumsy. I'm trying to understand how things should be set
up so that I don't have to take special action each time I log in. Do I
do some .login/.logout magic?
Or, why not just go without a DSA passphrase? The passphrase only
protects me from root, before whom I am rather powerless anyhow.
Also, the OMPI FAQ says authorized_keys should have 644 protection. Out
on the web, it appears people advise 600, which doesn't make sense to me
since it just has public keys in it anyhow. (My head is starting to spin.)
Kenneth Yoshimoto wrote:
After you start up ssh-agent once, check env for SSH_AUTH_SOCK
If you start a new session and the old ssh-agent is still running, try
setting SSH_AUTH_SOCK.
I think there are more refined utilities out there to handle this
situation...
On Fri, 19 Feb 2010, Eugene Loh wrote:
Date: Fri, 19 Feb 2010 13:19:13 -0800
From: Eugene Loh <eugene....@sun.com>
Reply-To: Open MPI Users <us...@open-mpi.org>
To: Open MPI Users <us...@open-mpi.org>
Subject: [OMPI users] password-less ssh
This is with regards to
http://www.open-mpi.org/faq/?category=rsh#ssh-keys
It says to check if you have an ssh-agent running. How are you
supposed to do that? I've tried "ps -u myusername | grep ssh-agent",
but didn't know if that's the proper thing to do.
Also, it appears that I do *NOT* have an ssh-agent running
automatically for me. How often do I have to start one up? It
appears that if I start one up and log out and then log back in
again, the old ssh-agent is still there but not usable. I have to
start up a new one. So, do I have to start an ssh-agent each time I
log in?
Or, I could use no DSA passphrase, but that seems to be frowned upon.
