blocks|key|20282|text|fish+shell的用户可以使用这个script来做同样的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|20283|#+content+has+to+be+in+.config/fish/config.fish
#+if+it+does+not+exist,+create+the+file
setenv+SSH_ENV+$HOME/.ssh/environment

function+start_agent++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++echo+"Initializing+new+SSH+agent+..."
++++ssh-agent+-c+%7C+sed+'s/%5Eecho/#echo/'+>+$SSH_ENV
++++echo+"succeeded"
++++chmod+600+$SSH_ENV+
++++.+$SSH_ENV+>+/dev/null
++++ssh-add
end

function+test_identities++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++ssh-add+-l+%7C+grep+"The+agent+has+no+identities"+>+/dev/null
++++if+[+$status+-eq+0+]
++++++++ssh-add
++++++++if+[+$status+-eq+2+]
++++++++++++start_agent
++++++++end
++++end
end

if+[+-n+"$SSH_AGENT_PID"+]+
++++ps+-ef+%7C+grep+$SSH_AGENT_PID+%7C+grep+ssh-agent+>+/dev/null
++++if+[+$status+-eq+0+]
++++++++test_identities
++++end++
else
++++if+[+-f+$SSH_ENV+]
++++++++.+$SSH_ENV+>+/dev/null
++++end++
++++ps+-ef+%7C+grep+$SSH_AGENT_PID+%7C+grep+-v+grep+%7C+grep+ssh-agent+>+/dev/null
++++if+[+$status+-eq+0+]
++++++++test_identities
++++else+
++++++++start_agent
++++end++
end|code-block|syntax|javascript|20284|entityMap|0|LINK|mutability|MUTABLE|url|http://fishshell.com/|1|https://gist.github.com/gerbsen/5fd8aa0fde87ac7a2cae^0|0|A|0|J|6|1|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|F|7|Z|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]|Q|$5|L|M|N|C|$O|R]]]]

Users of the <a href="http://fishshell.com/" rel="nofollow noreferrer">fish shell</a> can use this <a href="https://gist.github.com/gerbsen/5fd8aa0fde87ac7a2cae" rel="nofollow noreferrer">script</a> to do the same thing.

<pre class="lang-fish prettyprint-override"><code># content has to be in .config/fish/config.fish
# if it does not exist, create the file
setenv SSH_ENV $HOME/.ssh/environment

function start_agent 
 echo "Initializing new SSH agent ..."
 ssh-agent -c | sed 's/^echo/#echo/' &gt; $SSH_ENV
 echo "succeeded"
 chmod 600 $SSH_ENV 
 . $SSH_ENV &gt; /dev/null
 ssh-add
end

function test_identities 
 ssh-add -l | grep "The agent has no identities" &gt; /dev/null
 if [ $status -eq 0 ]
 ssh-add
 if [ $status -eq 2 ]
 start_agent
 end
 end
end

if [ -n "$SSH_AGENT_PID" ] 
 ps -ef | grep $SSH_AGENT_PID | grep ssh-agent &gt; /dev/null
 if [ $status -eq 0 ]
 test_identities
 end 
else
 if [ -f $SSH_ENV ]
 . $SSH_ENV &gt; /dev/null
 end 
 ps -ef | grep $SSH_AGENT_PID | grep -v grep | grep ssh-agent &gt; /dev/null
 if [ $status -eq 0 ]
 test_identities
 else 
 start_agent
 end 
end
</code></pre>

blocks|key|20328|text|因此，我过去常常使用上面描述的方法，但我更希望代理在我的最后一个bash会话结束时终止。这比其他解决方案要长一点，但这是我首选的方法。基本思想是第一个bash会话启动ssh-agent。然后，每个额外的bash会话检查配置文件(~/.ssh/.agent_env)。如果存在，并且有一个会话正在运行，则获取环境并在/tmp中创建到套接字文件的硬链接(需要位于与原始套接字文件相同的文件系统上)。当bash会话关闭时，每个会话都会删除自己的硬链接。最后一个关闭的会话将发现硬链接有2个链接(硬链接和原始)，移除进程自己的套接字并杀死进程将导致0，在最后一个bash会话关闭后留下一个干净的环境。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|20329|#+Start+ssh-agent+to+keep+you+logged+in+with+keys,+use+`ssh-add`+to+log+in
agent=`pgrep+ssh-agent+-u+$USER`+#+get+only+your+agents+++++++++++
if+[[+"$agent"+==+""+%7C%7C+!+-e+~/.ssh/.agent_env+]];+then
++++#+if+no+agents+or+environment+file+is+missing+create+a+new+one
++++#+remove+old+agents+/+environment+variable+files
++++kill+$agent+running
++++rm+~/.ssh/.agent_env+

++++#+restart
++++eval+`ssh-agent`+
++++echo+'export+SSH_AUTH_SOCK'=$SSH_AUTH_SOCK+>>+~/.ssh/.agent_env+++++++++++++
++++echo+'export+SSH_AGENT_PID'=$SSH_AGENT_PID+>>+~/.ssh/.agent_env+++++++++++++
fi

#+create+our+own+hardlink+to+the+socket+(with+random+name)+++++++++++
source+~/.ssh/.agent_env++++++++++++++++++++++++++++++++++++++++++++++++++++
MYSOCK=/tmp/ssh_agent.${RANDOM}.sock++++++++++++++++++++++++++++++++++++++++
ln+-T+$SSH_AUTH_SOCK+$MYSOCK++++++++++++++++++++++++++++++++++++++++++++++++
export+SSH_AUTH_SOCK=$MYSOCK++++++++++++++++++++++++++++++++++++++++++++++++

end_agent()+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
{
++++#+if+we+are+the+last+holder+of+a+hardlink,+then+kill+the+agent
++++nhard=`ls+-l+$SSH_AUTH_SOCK+%7C+awk+'{print+$2}'`+++++++++++++++++++++++++++++
++++if+[[+"$nhard"+-eq+2+]];+then+++++++++++++++++++++++++++++++++++++++++++++++
++++++++rm+~/.ssh/.agent_env++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++ssh-agent+-k++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++fi++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++rm+$SSH_AUTH_SOCK+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
}+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
trap+end_agent+EXIT+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
set+%2Bx++++++++++++++|code-block|syntax|javascript|20330|entityMap^0|36|H|4D|4|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

So I used to use the approaches described above, but I kind of prefer the agent to die when my last bash session ends. This is a bit longer than the other solutions, but its my preferred approach. The basic idea is that the first bash session starts the ssh-agent. Then each additional bash session checks for the config file (<code>~/.ssh/.agent_env</code>). If that is there and there is a session running then source the environment and create a hardlink to the socket file in <code>/tmp</code> (needs to be on the same filesystem as the original socket file). As bash sessions shut down each deletes its own hardlink. The last session to close will find that the hardlinks have 2 links (the hardlink and the original), removal of the processes own socket and killing of the process will result in 0, leaving a clean environment after the last bash session closes.

<pre class="lang-sh prettyprint-override"><code># Start ssh-agent to keep you logged in with keys, use `ssh-add` to log in
agent=`pgrep ssh-agent -u $USER` # get only your agents 
if [[ "$agent" == "" || ! -e ~/.ssh/.agent_env ]]; then
 # if no agents or environment file is missing create a new one
 # remove old agents / environment variable files
 kill $agent running
 rm ~/.ssh/.agent_env 

 # restart
 eval `ssh-agent` 
 echo 'export SSH_AUTH_SOCK'=$SSH_AUTH_SOCK &gt;&gt; ~/.ssh/.agent_env 
 echo 'export SSH_AGENT_PID'=$SSH_AGENT_PID &gt;&gt; ~/.ssh/.agent_env 
fi

# create our own hardlink to the socket (with random name) 
source ~/.ssh/.agent_env 
MYSOCK=/tmp/ssh_agent.${RANDOM}.sock 
ln -T $SSH_AUTH_SOCK $MYSOCK 
export SSH_AUTH_SOCK=$MYSOCK 

end_agent() 
{
 # if we are the last holder of a hardlink, then kill the agent
 nhard=`ls -l $SSH_AUTH_SOCK | awk '{print $2}'` 
 if [[ "$nhard" -eq 2 ]]; then 
 rm ~/.ssh/.agent_env 
 ssh-agent -k 
 fi 
 rm $SSH_AUTH_SOCK 
} 
trap end_agent EXIT 
set +x 
</code></pre>

blocks|key|20345|text|我很喜欢你的回答。它使得在cygwin+/+linux主机上工作变得容易得多。我组合了start和end函数来保证它的安全性。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|20346|SSH_ENV="$HOME/.ssh/.agent_env"

function+start_agent+{
++++echo+"Initialising+new+SSH+agent..."

++++eval+`/usr/bin/ssh-agent`
++++echo+'export+SSH_AUTH_SOCK'=$SSH_AUTH_SOCK+>>+${SSH_ENV}
++++echo+'export+SSH_AGENT_PID'=$SSH_AGENT_PID+>>+${SSH_ENV}

++++echo+succeeded
++++chmod+600+"${SSH_ENV}"
++++.+"${SSH_ENV}"+>+/dev/null
++++/usr/bin/ssh-add;
}

#+Source+SSH+settings,+if+applicable
if+[+-f+"${SSH_ENV}"+];+then
++++.+"${SSH_ENV}"+>+/dev/null
++++#ps+${SSH_AGENT_PID}+doesn't+work+under+cywgin
++++ps+-ef+%7C+grep+${SSH_AGENT_PID}+%7C+grep+ssh-agent$+>+/dev/null+%7C%7C+{
++++++++start_agent;
++++}
else
++++start_agent;
fi

#+create+our+own+hardlink+to+the+socket+(with+random+name)
MYSOCK=/tmp/ssh_agent.${RANDOM}.sock
ln+-T+$SSH_AUTH_SOCK+$MYSOCK
export+SSH_AUTH_SOCK=$MYSOCK

end_agent()
{
++++#+if+we+are+the+last+holder+of+a+hardlink,+then+kill+the+agent
++++nhard=`ls+-l+$SSH_AUTH_SOCK+%7C+awk+'{print+$2}'`
++++if+[[+"$nhard"+-eq+2+]];+then
++++++++rm+${SSH_ENV}
++++++++/usr/bin/ssh-agent+-k
++++fi
++++rm+$SSH_AUTH_SOCK
}
trap+end_agent+EXIT
set+%2Bx|code-block|syntax|javascript|20347|entityMap^0|D|E|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

I like your answers a lot. It made working from <code>cygwin / linux</code> hosts a lot easier. I combined start and end functions to make it secure.

<pre class="lang-sh prettyprint-override"><code>SSH_ENV="$HOME/.ssh/.agent_env"

function start_agent {
 echo "Initialising new SSH agent..."

 eval `/usr/bin/ssh-agent`
 echo 'export SSH_AUTH_SOCK'=$SSH_AUTH_SOCK &gt;&gt; ${SSH_ENV}
 echo 'export SSH_AGENT_PID'=$SSH_AGENT_PID &gt;&gt; ${SSH_ENV}

 echo succeeded
 chmod 600 "${SSH_ENV}"
 . "${SSH_ENV}" &gt; /dev/null
 /usr/bin/ssh-add;
}

# Source SSH settings, if applicable
if [ -f "${SSH_ENV}" ]; then
 . "${SSH_ENV}" &gt; /dev/null
 #ps ${SSH_AGENT_PID} doesn't work under cywgin
 ps -ef | grep ${SSH_AGENT_PID} | grep ssh-agent$ &gt; /dev/null || {
 start_agent;
 }
else
 start_agent;
fi

# create our own hardlink to the socket (with random name)
MYSOCK=/tmp/ssh_agent.${RANDOM}.sock
ln -T $SSH_AUTH_SOCK $MYSOCK
export SSH_AUTH_SOCK=$MYSOCK

end_agent()
{
 # if we are the last holder of a hardlink, then kill the agent
 nhard=`ls -l $SSH_AUTH_SOCK | awk '{print $2}'`
 if [[ "$nhard" -eq 2 ]]; then
 rm ${SSH_ENV}
 /usr/bin/ssh-agent -k
 fi
 rm $SSH_AUTH_SOCK
}
trap end_agent EXIT
set +x
</code></pre>

blocks|key|20358|text|将其添加到您的~/.bashrc中，然后注销并重新登录才能生效。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|20359|if+[+!+-S+~/.ssh/ssh_auth_sock+];+then
++eval+`ssh-agent`
++ln+-sf+"$SSH_AUTH_SOCK"+~/.ssh/ssh_auth_sock
fi
export+SSH_AUTH_SOCK=~/.ssh/ssh_auth_sock
ssh-add+-l+>+/dev/null+%7C%7C+ssh-add|code-block|syntax|javascript|20360|这应该只会在您每次重新启动后第一次登录时提示输入密码。只要它保持运行，它就会一直重用相同的ssh-agent。|20361|entityMap^0|7|9|0|0|19|9|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

Add this to your <code>~/.bashrc</code>, then logout and back in to take effect.

<pre class="lang-bash prettyprint-override"><code>if [ ! -S ~/.ssh/ssh_auth_sock ]; then
 eval `ssh-agent`
 ln -sf "$SSH_AUTH_SOCK" ~/.ssh/ssh_auth_sock
fi
export SSH_AUTH_SOCK=~/.ssh/ssh_auth_sock
ssh-add -l &gt; /dev/null || ssh-add
</code></pre>

This should only prompt for a password the first time you login after each reboot. It will keep reusing the same <code>ssh-agent</code> as long as it stays running.

blocks|key|20396|text|在Arch+Linux上，下面的工作非常棒(应该可以在所有基于systemd的发行版上工作)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|20397|通过将以下内容放入~/.config/systemd/user/ssh-agent.service，创建一个systemd用户服务|offset|length|style|CODE|20398|[Unit]
Description=SSH+key+agent

[Service]
Type=simple
Environment=SSH_AUTH_SOCK=%25t/ssh-agent.socket
ExecStart=/usr/bin/ssh-agent+-D+-a+$SSH_AUTH_SOCK

[Install]
WantedBy=default.target|code-block|syntax|javascript|20399|将shell设置为具有套接字的环境变量(.bash_profile,+.zshrc,+...)：|20400|export+SSH_AUTH_SOCK="$XDG_RUNTIME_DIR/ssh-agent.socket"|20401|启用服务，这样它将在登录时自动启动，并启动它：|20402|systemctl+--user+enable+ssh-agent
systemctl+--user+start+ssh-agent|20403|将以下配置设置添加到本地ssh配置文件~/.ssh/config+(自SSH7.2起即可使用)：|20404|AddKeysToAgent++yes|20405|这将指示ssh客户端始终将密钥添加到正在运行的代理中，因此不需要事先使用ssh添加密钥。|20406|entityMap^0|0|9|14|0|0|K|Q|0|0|0|0|J|D|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|16|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|17|8|@$D|18|E|19|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|1A|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|T|5|J|7|1C|8|@]|9|@]|A|$K|L]]|$1|U|3|V|5|6|7|1D|8|@$D|1E|E|1F|F|G]]|9|@]|A|$]]|$1|W|3|X|5|J|7|1G|8|@]|9|@]|A|$K|L]]|$1|Y|3|Z|5|6|7|1H|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|11|$]]

On Arch Linux, the following works really great (should work on all systemd-based distros):

Create a systemd user service, by putting the following to <code>~/.config/systemd/user/ssh-agent.service</code>:

<pre><code>[Unit]
Description=SSH key agent

[Service]
Type=simple
Environment=SSH_AUTH_SOCK=%t/ssh-agent.socket
ExecStart=/usr/bin/ssh-agent -D -a $SSH_AUTH_SOCK

[Install]
WantedBy=default.target
</code></pre>

Setup shell to have an environment variable for the socket (<code>.bash_profile, .zshrc, ...</code>):

<pre><code>export SSH_AUTH_SOCK="$XDG_RUNTIME_DIR/ssh-agent.socket"
</code></pre>

Enable the service, so it'll be started automatically on login, and start it:

<pre><code>systemctl --user enable ssh-agent
systemctl --user start ssh-agent
</code></pre>

Add the following configuration setting to your local ssh config file <code>~/.ssh/config</code> (this works since SSH 7.2):

<pre><code>AddKeysToAgent yes
</code></pre>

This will instruct the ssh client to always add the key to a running agent, so there's no need to ssh-add it beforehand.

I have a site as a remote Git repo pulling from Bitbucket.com using an SSH alias. I can manually start the ssh-agent on my server but I have to do this every time I login via SSH.

I manually start the ssh-agent:

<pre><code>eval ssh-agent $SHELL
</code></pre>

Then I add the agent:

<pre><code>ssh-add ~/.ssh/bitbucket_id
</code></pre>

Then it shows up when I do:

<pre><code>ssh-add -l
</code></pre>

And I'm good to go. Is there any way to automate this process so I don't have to do it every time I login? The server is running RedHat 6.2 (Santiago).

Start ssh-agent on login

文件系统

Arch Linux

服务器

Bitbucket

Linux

我有一个网站作为远程Git repo，使用SSH别名从Bitbucket.com拉取。我可以在服务器上手动启动ssh-agent，但每次通过SSH登录时都必须这样做。我手动启动ssh-agent：eval ssh-agent $SHELL然后添加代理：ssh-add ~/.ssh/bitbucket_id然后，当我这样...

问登录时启动ssh-agent
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问登录时启动ssh-agentEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问登录时启动ssh-agent
EN