Skip to main content

ssh - automatically start or attach to ssh-agent

Managing mulltiple ssh-key pairs can be made easy by utilizing the power of ssh-agent. However, I'd like to have my ssh-sessions automatically attach to the ssh-agent or start a instance of ssh-agent if it's not already started.
Starting the ssh-agent and attaching to it can be achieved by using these commands:
 [archy@server ~]$ ssh-agent -s > ${HOME}/.ssh/environment-$(hostname -s)  
 [archy@server ~]$ source ${HOME}/.ssh/environment-$(hostname -s)  
This will create a file named 'environment-server' in the folder ~/.ssh with all information required to attach it and then source it to attach to the running ssh-agent.

Reconnecting to the running ssh-agent can be done using this command again:
 [archy@server ~]$ source ${HOME}/.ssh/environment-$(hostname -s)  
Another thing to consider is not starting multiple ssh-agents, so we'll have to check there is a instance of ssh-agent running for the current user and then determine if we should attach to the currently running instance or stop it and restart it by using the method mentioned above, here's a code-snippet that can help with that:
 AGENTPID=$(pgrep -u ${USER} -x ssh-agent)  
 PGREP_RC=$?  
 if [ ${PGREP_RC} -eq 0 ]; then  
  if [ -f ${HOME}/.ssh/environment-$(hostname -s) ]; then  
   echo -e "attaching to ssh-agent for user ${USER}"  
   source ${HOME}/.ssh/environment-$(hostname -s)  
  else  
   echo -e "killing stale agent for user ${USER}"  
   kill -s TERM ${AGENTPID}  
   ssh-agent -s > ${HOME}/.ssh/environment-$(hostname -s)  
   source ${HOME}/.ssh/environment-$(hostname -s)  
  fi  
 fi  
Now, let's throw it all together:
 AGENTPID=$(pgrep -u ${USER} -x ssh-agent)  
 PGREP_RC=$?  
 if [ ${PGREP_RC} -eq 0 ]; then  
  if [ -f ${HOME}/.ssh/environment-$(hostname -s) ]; then  
   echo -e "attaching to ssh-agent for user ${USER}"  
   source ${HOME}/.ssh/environment-$(hostname -s)  
  else  
   echo -e "killing stale agent for user ${USER}"  
   kill -s TERM ${AGENTPID}  
   ssh-agent -s > ${HOME}/.ssh/environment-$(hostname -s)  
   source ${HOME}/.ssh/environment-$(hostname -s)  
  fi   
 else  
  echo -e "starting ssh-agent for user ${USER}"  
  ssh-agent -s > ${HOME}/.ssh/environment-$(hostname -s)  
  source ${HOME}/.ssh/environment-$(hostname -s)  
  export SSH_AGENT  
 fi  
And now to make it automatic, add it to your shellrc so that it will be executed on every login. In my case, I want this to apply serverwide, so I'll add it to /etc/zshrc. I'll also add a check to ensure that ~/.ssh exists:
 [archy@server ~]$ sudo vim /etc/zshrc
 # start - attach or start ssh-agent                                                
 if [ ! -d ${HOME}/.ssh ]; then  
  mkdir -p -m 750 ${HOME}/.ssh  
 fi                 
 AGENTPID=$(pgrep -u ${USER} -x ssh-agent)  
 PGREP_RC=$?              
 if [ ${PGREP_RC} -eq 0 ]; then  
  if [ -f ${HOME}/.ssh/environment-$(hostname -s) ]; then  
   echo -e "attaching to ssh-agent for user ${USER}"  
   source ${HOME}/.ssh/environment-$(hostname -s)  
  else  
   echo -e "killing stale agent for user ${USER}"  
   kill -s TERM ${AGENTPID}  
   ssh-agent -s > ${HOME}/.ssh/environment-$(hostname -s)  
   source ${HOME}/.ssh/environment-$(hostname -s)  
  fi  
 else  
  echo -e "starting ssh-agent for user ${USER}"  
  ssh-agent -s > ${HOME}/.ssh/environment-$(hostname -s)  
  source ${HOME}/.ssh/environment-$(hostname -s)  
  export SSH_AGENT  
 fi  
 # stop - attach or start ssh-agent  
On login, you'll then see a message like this:
 attaching to ssh-agent for user archy  
 Agent pid 123456  
I am well aware that there is a package manager for zsh (oh-my-zsh) which offers packages that can do this for you but I'm purposefully trying to stay away from oh-my-zsh because it is overkill for my use-case.

Feel free to comment and / or suggest a topic.


Comments

Popular posts from this blog

Dynamic DNS with BIND and ISC-DHCP

I personally prefer to work with hostnames instead of ip-addresses. If you have anything like freeipa or active directory, it will do that for you by registering the client you added to your realm to the managed dns and edit the records dynamically. We can achieve the same goal with just bind and isc-dhcp. I'll use a raspberry pi with raspbian 9 for this setup. So here is a quick tutorial on how to configure the isc-dhcp-server to dynamically update bind. First set a static ip to your server. [archy@ddns ~]$ sudo vim /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto eth0 iface eth0 inet static address 172.31.30.5 network 172.31.30.0 broadcast 172.31.30.255 netmask 255.255.255.0 ...

LACP-Teaming on CentOS 7 / RHEL 7

What is teaming? Teaming or LACP (802.3ad) is a technique used to bond together multiple interfaces to achieve higher combined bandwith. NOTE: every clients speed can only be as high as the single link speed of one of the members. That means, if the interfaces I use in the bond have 1 Gigabit, every client will only have a maximum speed of 1 Gigabit. The advantage of teaming is, that it can handle multiple connections with 1 Gigabit. How many connections depends on the amount of your network cards. I'm using 2 network cards for this team on my server. That means I can handle 2 Gigabit connections at full rate on my server provided the rest of the hardware can deliver that speed. There also exists 'Bonding' in the Linux world. They both do the same in theory but  for a detailed comparison check out this  article about teaming in RHEL7 . To create a teaming-interface, we will first have to remove all the interface configurations we've done on the (soon to be) sla...

Push logs and data into elasticsearch - Part 2 Mikrotik Logs

This is only about the setup of different logging, one being done with Filebeat and the other being done with sending logging to a dedicated port opened in Logstash using the TCP / UDP Inputs. Prerequesites: You'll need a working Elasticsearch Cluster with Logstash and Kibana. Start by getting the Log Data you want to structure parsed correctly. Mikrotik Logs are a bit difficult since they show you Data in the interface which is already enriched with Time / Date. That means a message that the remote logging will send to Logstash will look like this: firewall,info forward: in:lan out:wan, src-mac aa:bb:cc:dd:ee:ff, proto UDP, 172.31.100.154:57061->109.164.113.231:443, len 76 You can check them in the grok debugger and create your own filters and mapping. The following is my example which might not fit your needs. Here are some custom patterns I wrote for my pattern matching: MIKROTIK_DATE \b(?:jan(?:uary)?|feb(?:ruary)?|mar(?:ch)?|apr(?:il)?|may|jun(?:e)?|jul(?...

FreeIPA - Integrating your DHCPD dynamic Updates into IPA

I recently went over my network configuration and noticed that the dhcp-leases were not pushed into the IPA-DNS yet. So I thought, why not do it now. The setup is very similar to setting it up on a single bind instance not managed by IPA (I've already written a guide about this here ). My setup is done with the following hosts: ipa01.archyslife.lan - 172.31.0.1 inf01.archyslife.lan - 172.31.0.5 First of all, create a rndc-key: [archy@ipa01 ~]$ sudo rndc-confgen -a -b 512 This will create the following file '/etc/rndc-key' [archy@ipa01 ~]$ sudo cat /etc/rndc.key key "rndc-key" { algorithm hmac-md5; secret "secret_key_here=="; }; We also need to make named aware of the rndc-key and allow our remote dhcp server to write dns entries: [archy@ipa01 ~]$ sudo vim /etc/named.conf ... include "/etc/rndc-key"; controls { inet 172.31.0.1 port 953 allow { 172.31.0.5; } keys ...

SSSD - Debugging PAM permission denied

Sometimes there's weird errors in IT that occur on random chance. I've had such an encounter with SSSD in combination with IPA(+AD-Trust) recently, where only sometimes, a connection to one of the IPA-Servers would fail with this error: Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: pam_sss(sshd:account): Access denied for user runner: 4 (System error) Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: fatal: Access denied for user runner by PAM account configuration [preauth] In my case, it was only happening sometimes when running a basic system setup role using ansible on every host in the entire environment. This way, there was no consistent pattern besides being the same host every time if it failed. First up, add the 'debug_level=X' to every section required in the /etc/sssd/sssd.conf where X is a number from 1 to 10 with 10 being the most verbose. Afterward, restart sssd and check the logs for any obvious problems. 1) If you are using local users, check the...