| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Ensure filenames with spaces don't make the sample script choke
|
|
gh-pages
Conflicts:
_posts/2009-09-03-working-with-key-passphrases.textile
|
|
|
|
Changed the grep check from simply ignoring its own entry, i.e., grep -v grep to
checking that the process running under the SSH_AGENT_PID is actually an
ssh-agent.
|
|
|
|
The automatic launching now first checks for an already running agent before it
launches its own one. Launching is now consistent across windows due to the use
of SSH_ENV again. The return code of ssh-add is now specifically checked for
returncode 2 which indicates that the socket is broken.
|
|
The idea is to have a single ssh-agent instance that holds all the keys.
Checking and spawning of ssh-agents should be consistent now.
|
|
The variable SSH_AGENT_PID might still be set, so it should not be used for
testing. Resorted to a ps test instead.
|
|
I modified the script for automatic ssh-agent starting to only start a new agent
if one isn't running already and to only add the keys from standard file
locations only if the agent doesn't already contain any identities.
The reasoning for me was that every time I open a new bash window or fire up
'screen', I would be asked for the passphrase.
|
|
|
|
|
|
|
