SSH/Keys - Revision history

Mbaney at 14:35, 21 March 2025

2025-03-21T14:35:12Z

← Older revision		Revision as of 14:35, 21 March 2025
Line 2:		Line 2:

	==Overview==		==Overview==
	'''Note: UMIACS still requires multi-factor authentication if you are connecting from the public internet or a [[VPN]] for security reasons. SSH keys can only be used when connecting to a UMIACS-supported host from another UMIACS~~-supported host~~.'''		'''Note: UMIACS still requires multi-factor authentication if you are connecting from the public internet or a [[VPN]] for security reasons. SSH keys can only be used when connecting to a UMIACS-supported host from another host already within UMIACS' network border.'''

	; Prerequisites		; Prerequisites

Mbaney at 14:29, 21 March 2025

2025-03-21T14:29:03Z

← Older revision		Revision as of 14:29, 21 March 2025
Line 2:		Line 2:

	==Overview==		==Overview==
			'''Note: UMIACS still requires multi-factor authentication if you are connecting from the public internet or a [[VPN]] for security reasons. SSH keys can only be used when connecting to a UMIACS-supported host from another UMIACS-supported host.'''

	; Prerequisites		; Prerequisites
	# If using batch clusters (e.g. [[SLURM]]) please read [[SSH/Keys#Batch clusters \| Batch clusters]] prior to creating a new key.		# If using batch clusters (e.g. [[SLURM]]) please read [[SSH/Keys#Batch clusters \| Batch clusters]] prior to creating a new key.
Line 16:		Line 18:
	# [[SSH/Keys#Copy the public key \| Copy the public key]]		# [[SSH/Keys#Copy the public key \| Copy the public key]]
	# If Windows, [[SSH/Keys#Adding Keys to SSH Clients (Windows Only) \| Adding Keys to SSH Clients (Windows Only)]]		# If Windows, [[SSH/Keys#Adding Keys to SSH Clients (Windows Only) \| Adding Keys to SSH Clients (Windows Only)]]

	~~'''Note: UMIACS still requires multi-factor authentication if you are connecting from the public internet for security reasons.'''~~

	; Additional Considerations		; Additional Considerations

Mbaney at 15:54, 20 February 2025

2025-02-20T15:54:48Z

← Older revision		Revision as of 15:54, 20 February 2025
Line 2:		Line 2:

	==Overview==		==Overview==
	;Prerequisites		; Prerequisites
	#If using batch clusters (e.g. [[SLURM]]) please read [[SSH/Keys#Batch clusters \| Batch clusters]] prior to creating a new key.		# If using batch clusters (e.g. [[SLURM]]) please read [[SSH/Keys#Batch clusters \| Batch clusters]] prior to creating a new key.
	#Determine your OS (and if Windows, what you will be using to create the key)		# Determine your OS (and if Windows, what you will be using to create the key)
	#*Windows		#* Windows
	#**Git Bash: follow instructions for Linux/MacOS/Bash and Git Bash (for Windows)		#** Git Bash: follow instructions for Linux/MacOS/Bash and Git Bash (for Windows)
	#**PuTTY: follow instructions for Windows (and PuTTY subsections)		#** PuTTY: follow instructions for Windows (and PuTTY subsections)
	#**TTSSH2: follow instructions for Windows (and TTSSH2 subsections)		#** TTSSH2: follow instructions for Windows (and TTSSH2 subsections)
	#**[[BashForWindows10 \| Windows Subsystem for Linux (WSL)]]: follow instructions for 'Linux/MacOS/Bash and Git Bash (for Windows)'		#** [[BashForWindows10 \| Windows Subsystem for Linux (WSL)]]: follow instructions for 'Linux/MacOS/Bash and Git Bash (for Windows)'
	#*Linux: follow instructions for 'Linux/MacOS/Bash and Git Bash (for Windows)'		#* Linux: follow instructions for 'Linux/MacOS/Bash and Git Bash (for Windows)'
	#*MacOS: follow instructions for 'Linux/MacOS/Bash and Git Bash (for Windows)'		#* MacOS: follow instructions for 'Linux/MacOS/Bash and Git Bash (for Windows)'
	;Steps		; Steps
	#[[SSH/Keys#Create and store the key pair \| Create and store the key pair]]		# [[SSH/Keys#Create and store the key pair \| Create and store the key pair]]
	#[[SSH/Keys#Copy the public key \| Copy the public key]]		# [[SSH/Keys#Copy the public key \| Copy the public key]]
	#If Windows, [[SSH/Keys#Adding Keys to SSH Clients (Windows Only) \| Adding Keys to SSH Clients (Windows Only)]]		# If Windows, [[SSH/Keys#Adding Keys to SSH Clients (Windows Only) \| Adding Keys to SSH Clients (Windows Only)]]

	'''Note: UMIACS still requires multi-factor authentication if you are connecting from the public internet for security reasons~~. If you first connect to our VPN, you should then be able to use the keys as normal~~.'''		'''Note: UMIACS still requires multi-factor authentication if you are connecting from the public internet for security reasons.'''

	;Additional Considerations		; Additional Considerations
	#The [[SSH/Keys#SSH Agents \| SSH Agents]] section is not a required component of creating and using an SSH key, but can be very useful if you choose to create a password to protect your SSH key, but find yourself needing to enter that password many times in a session. [[SSH/Keys#SSH Agents \| SSH Agents]] allow you to temporarily use your SSH key without a password for a set period of time. Please see the [[SSH/Keys#SSH Agents \| SSH Agents]] section for more information.		# The [[SSH/Keys#SSH Agents \| SSH Agents]] section is not a required component of creating and using an SSH key, but can be very useful if you choose to create a password to protect your SSH key, but find yourself needing to enter that password many times in a session. [[SSH/Keys#SSH Agents \| SSH Agents]] allow you to temporarily use your SSH key without a password for a set period of time. Please see the [[SSH/Keys#SSH Agents \| SSH Agents]] section for more information.

	==Create and store the key pair==		==Create and store the key pair==

	The first step is to generate a key which will create two files filled with long strings of characters. A public key file that you may distribute to any machine you want to use it on and a private key that needs to be kept secure. '''Allowing anyone to read this private key will compromise the security of the key and could allow someone to access any resources secured by this key without your consent.''' There are a number of different key types but <code>rsa</code> is the most compatible.		The first step is to generate a key which will create two files filled with long strings of characters. A public key file that you may distribute to any machine you want to use it on and a private key that needs to be kept secure. '''Allowing anyone to read this private key will compromise the security of the key and could allow someone to access any resources secured by this key without your consent.''' There are a number of different key types but <code>rsa</code> is the most compatible.

	===Windows===		===Windows===
	;Git Bash		; Git Bash
	:See [[SSH/Keys#Linux.2FMacOS.2FBash_and_Git_Bash_.28for_Windows.29 \| Linux/MacOS/Bash and Git Bash (for Windows)]]		: See [[SSH/Keys#Linux.2FMacOS.2FBash_and_Git_Bash_.28for_Windows.29 \| Linux/MacOS/Bash and Git Bash (for Windows)]]
	;PuTTY		; PuTTY
	# Click on the start menu and search for PuTTYgen. Open the application		# Click on the start menu and search for PuTTYgen. Open the application.
	# Verify that you are attempting to create an "SSH2 RSA" key by clicking on the appropriate box		# Verify that you are attempting to create an "SSH2 RSA" key by clicking on the appropriate box.
	# Click generate and follow the instructions for generating your keys		# Click generate and follow the instructions for generating your keys.
	# Add passphrase if wanted and save both the public and private keys		# Add passphrase if wanted and save both the public and private keys.
	;TTSSH2		; TTSSH2
	# Open the application		# Open the application.
	# Cancel the first box		# Cancel the first box.
	# Go to setup on the menu bar and go to SSH KeyGenerator		# Go to setup on the menu bar and go to SSH KeyGenerator.
	# Click generate and follow the instructions for generating your key		# Click generate and follow the instructions for generating your key.
	# Add passphrase if wanted and save both the public and private keys		# Add passphrase if wanted and save both the public and private keys.

	===Linux/MacOS/Bash and Git Bash (for Windows)===		===Linux/MacOS/Bash and Git Bash (for Windows)===
	;Create a new key with a password		; Create a new key with a password
	You can run the command <code>ssh-keygen -t rsa</code> to generate the new public and private key. It will prompt you for a file to create the private key and then for the public key append <code>.pub</code> extension and store it in the same directory. Pressing enter at the passphrase step twice will create a key without a pass-phrase.		You can run the command <code>ssh-keygen -t rsa</code> to generate the new public and private key. It will prompt you for a file to create the private key and then for the public key append <code>.pub</code> extension and store it in the same directory. Pressing enter at the passphrase step twice will create a key without a pass-phrase.

Line 100:		Line 99:
	</pre>		</pre>

	;Modify permissions		; Modify permissions
	Modify the permissions of your <tt>.ssh</tt> directory as well as the private key file that you just created with <tt>chmod</tt>.		Modify the permissions of your <tt>.ssh</tt> directory as well as the private key file that you just created with <tt>chmod</tt>.

Line 132:		Line 131:

	==Adding Keys to SSH Clients (Windows Only)==		==Adding Keys to SSH Clients (Windows Only)==
	;PuTTY		; PuTTY
	# Open PuTTY and enter the [https://en.wikipedia.org/wiki/Fully_qualified_domain_name fully qualified domain name (FQDN)] for the host you wish to connect to.		# Open PuTTY and enter the [https://en.wikipedia.org/wiki/Fully_qualified_domain_name fully qualified domain name (FQDN)] for the host you wish to connect to.
	# Go to the Connections tab on the side panel and click on the data subsection.		# Go to the Connections tab on the side panel and click on the data subsection.
Line 139:		Line 138:
	# Under Auth click on the browse and navigate to the saved private key.		# Under Auth click on the browse and navigate to the saved private key.
	# Go back to session on the side panel and save your settings by typing in a name in saved sessions pressing the save button.		# Go back to session on the side panel and save your settings by typing in a name in saved sessions pressing the save button.
	;TTSSH2		; TTSSH2
	# Open the application.		# Open the application.
	# Cancel the first box.		# Cancel the first box.

Mbaney at 19:04, 3 June 2024

2024-06-03T19:04:55Z

← Older revision		Revision as of 19:04, 3 June 2024
Line 117:		Line 117:

	===Linux/MacOS/Bash and Git Bash (for Windows)===		===Linux/MacOS/Bash and Git Bash (for Windows)===
	This can be done with the <code>ssh-copy-id</code> command and it will prompt you the first time for your current password ('''NOT your pass-phrase'''). You can replace localhost with any other hostname you want to copy the key to. You can also specify a alternate user or identity file if you need to, please <code>man ssh-copy-id</code> for more information within your terminal. This command will ensure that not only it copies your key but secures the file so that no one can tamper and add additional authorized keys to the file on the remote host.		This can be done with the <code>ssh-copy-id</code> command and it will prompt you the first time for your current password ('''NOT your pass-phrase'''). You can replace localhost with any other hostname you want to copy the key to. You can also specify an alternate user or identity file if you need to, please <code>man ssh-copy-id</code> for more information within your terminal. This command will ensure that not only it copies your key but secures the file so that no one can tamper and add additional authorized keys to the file on the remote host.

	Example: <pre>		Example: <pre>

Mbaney: /* Adding Keys to SSH Clients (Windows Only) */

2024-06-03T19:04:32Z

Adding Keys to SSH Clients (Windows Only)

← Older revision		Revision as of 19:04, 3 June 2024
Line 133:		Line 133:
	==Adding Keys to SSH Clients (Windows Only)==		==Adding Keys to SSH Clients (Windows Only)==
	;PuTTY		;PuTTY
	# Open PuTTY and enter the ~~Fully Qualified Domain Name~~ for the host you wish to connect to.		# Open PuTTY and enter the [https://en.wikipedia.org/wiki/Fully_qualified_domain_name fully qualified domain name (FQDN)] for the host you wish to connect to.
	# Go to the Connections tab on the side panel and click on the data subsection.		# Go to the Connections tab on the side panel and click on the data subsection.
	# Under data enter your default user into the first box. (Auto-login Username)		# Under data enter your default user into the first box. (Auto-login Username)

Jishjesu at 20:23, 6 November 2023

2023-11-06T20:23:18Z

← Older revision		Revision as of 20:23, 6 November 2023
Line 16:		Line 16:
	#[[SSH/Keys#Copy the public key \| Copy the public key]]		#[[SSH/Keys#Copy the public key \| Copy the public key]]
	#If Windows, [[SSH/Keys#Adding Keys to SSH Clients (Windows Only) \| Adding Keys to SSH Clients (Windows Only)]]		#If Windows, [[SSH/Keys#Adding Keys to SSH Clients (Windows Only) \| Adding Keys to SSH Clients (Windows Only)]]

			'''Note: UMIACS still requires multi-factor authentication if you are connecting from the public internet for security reasons. If you first connect to our VPN, you should then be able to use the keys as normal.'''

	;Additional Considerations		;Additional Considerations
	#The [[SSH/Keys#SSH Agents \| SSH Agents]] section is not a required component of creating and using an SSH key, but can be very useful if you choose to create a password to protect your SSH key, but find yourself needing to enter that password many times in a session. [[SSH/Keys#SSH Agents \| SSH Agents]] allow you to temporarily use your SSH key without a password for a set period of time. Please see the [[SSH/Keys#SSH Agents \| SSH Agents]] section for more information.		#The [[SSH/Keys#SSH Agents \| SSH Agents]] section is not a required component of creating and using an SSH key, but can be very useful if you choose to create a password to protect your SSH key, but find yourself needing to enter that password many times in a session. [[SSH/Keys#SSH Agents \| SSH Agents]] allow you to temporarily use your SSH key without a password for a set period of time. Please see the [[SSH/Keys#SSH Agents \| SSH Agents]] section for more information.

Osalami at 02:57, 21 May 2023

2023-05-21T02:57:50Z

← Older revision		Revision as of 02:57, 21 May 2023
Line 6:		Line 6:
	#Determine your OS (and if Windows, what you will be using to create the key)		#Determine your OS (and if Windows, what you will be using to create the key)
	#*Windows		#*Windows
	#**Git Bash: follow instructions for Linux/~~MacOSX~~/Bash and Git Bash (for Windows)		#**Git Bash: follow instructions for Linux/MacOS/Bash and Git Bash (for Windows)
	#**PuTTY: follow instructions for Windows (and PuTTY subsections)		#**PuTTY: follow instructions for Windows (and PuTTY subsections)
	#**TTSSH2: follow instructions for Windows (and TTSSH2 subsections)		#**TTSSH2: follow instructions for Windows (and TTSSH2 subsections)
	#**[[BashForWindows10 \| Windows Subsystem for Linux (WSL)]]: follow instructions for 'Linux/~~MacOSX~~/Bash and Git Bash (for Windows)'		#**[[BashForWindows10 \| Windows Subsystem for Linux (WSL)]]: follow instructions for 'Linux/MacOS/Bash and Git Bash (for Windows)'
	#*Linux: follow instructions for 'Linux/~~MacOSX~~/Bash and Git Bash (for Windows)'		#*Linux: follow instructions for 'Linux/MacOS/Bash and Git Bash (for Windows)'
	#*~~MacOSX~~: follow instructions for 'Linux/~~MacOSX~~/Bash and Git Bash (for Windows)'		#*MacOS: follow instructions for 'Linux/MacOS/Bash and Git Bash (for Windows)'
	;Steps		;Steps
	#[[SSH/Keys#Create and store the key pair \| Create and store the key pair]]		#[[SSH/Keys#Create and store the key pair \| Create and store the key pair]]
Line 25:		Line 25:
	===Windows===		===Windows===
	;Git Bash		;Git Bash
	:See [[SSH/Keys#Linux.~~2FMacOSX~~.2FBash_and_Git_Bash_.28for_Windows.29 \| Linux/~~MacOSX~~/Bash and Git Bash (for Windows)]]		:See [[SSH/Keys#Linux.2FMacOS.2FBash_and_Git_Bash_.28for_Windows.29 \| Linux/MacOS/Bash and Git Bash (for Windows)]]
	;PuTTY		;PuTTY
	# Click on the start menu and search for PuTTYgen. Open the application		# Click on the start menu and search for PuTTYgen. Open the application
Line 38:		Line 38:
	# Add passphrase if wanted and save both the public and private keys		# Add passphrase if wanted and save both the public and private keys

	===Linux/~~MacOSX~~/Bash and Git Bash (for Windows)===		===Linux/MacOS/Bash and Git Bash (for Windows)===
	;Create a new key with a password		;Create a new key with a password
	You can run the command <code>ssh-keygen -t rsa</code> to generate the new public and private key. It will prompt you for a file to create the private key and then for the public key append <code>.pub</code> extension and store it in the same directory. Pressing enter at the passphrase step twice will create a key without a pass-phrase.		You can run the command <code>ssh-keygen -t rsa</code> to generate the new public and private key. It will prompt you for a file to create the private key and then for the public key append <code>.pub</code> extension and store it in the same directory. Pressing enter at the passphrase step twice will create a key without a pass-phrase.
Line 113:		Line 113:
	For Windows hosts you can use [http://winscp.net/eng/download.php WinSCP] to copy the public key file onto a remote host. The root file system for the Bash Subsystem for Windows is located under C:\Users\username>\AppData\Local\lxss\		For Windows hosts you can use [http://winscp.net/eng/download.php WinSCP] to copy the public key file onto a remote host. The root file system for the Bash Subsystem for Windows is located under C:\Users\username>\AppData\Local\lxss\

	===Linux/~~MacOSX~~/Bash and Git Bash (for Windows)===		===Linux/MacOS/Bash and Git Bash (for Windows)===
	This can be done with the <code>ssh-copy-id</code> command and it will prompt you the first time for your current password ('''NOT your pass-phrase'''). You can replace localhost with any other hostname you want to copy the key to. You can also specify a alternate user or identity file if you need to, please <code>man ssh-copy-id</code> for more information within your terminal. This command will ensure that not only it copies your key but secures the file so that no one can tamper and add additional authorized keys to the file on the remote host.		This can be done with the <code>ssh-copy-id</code> command and it will prompt you the first time for your current password ('''NOT your pass-phrase'''). You can replace localhost with any other hostname you want to copy the key to. You can also specify a alternate user or identity file if you need to, please <code>man ssh-copy-id</code> for more information within your terminal. This command will ensure that not only it copies your key but secures the file so that no one can tamper and add additional authorized keys to the file on the remote host.

Mbaney at 15:41, 7 May 2021

2021-05-07T15:41:17Z

← Older revision		Revision as of 15:41, 7 May 2021
Line 47:		Line 47:
	-bash-4.2$ ssh-keygen -t rsa		-bash-4.2$ ssh-keygen -t rsa
	Generating public/private rsa key pair.		Generating public/private rsa key pair.
	Enter file in which to save the key (/home/~~derek~~/.ssh/id_rsa):		Enter file in which to save the key (/home/username/.ssh/id_rsa):
	Created directory '/home/~~derek~~/.ssh'.		Created directory '/home/username/.ssh'.
	Enter passphrase (empty for no passphrase):		Enter passphrase (empty for no passphrase):
	Enter same passphrase again:		Enter same passphrase again:
	Your identification has been saved in /home/~~derek~~/.ssh/id_rsa.		Your identification has been saved in /home/username/.ssh/id_rsa.
	Your public key has been saved in /home/~~derek~~/.ssh/id_rsa.pub.		Your public key has been saved in /home/username/.ssh/id_rsa.pub.
	The key fingerprint is:		The key fingerprint is:
	32:bf:db:74:1b:7e:d7:c6:4b:b5:6f:a8:82:55:3f:bf ~~derek~~@localhost.localdomain		32:bf:db:74:1b:7e:d7:c6:4b:b5:6f:a8:82:55:3f:bf username@localhost.localdomain
	The key's randomart image is:		The key's randomart image is:
	+--[ RSA 2048]----+		+--[ RSA 2048]----+
Line 77:		Line 77:
	-bash-4.2$ ssh-keygen -t rsa -N ""		-bash-4.2$ ssh-keygen -t rsa -N ""
	Generating public/private rsa key pair.		Generating public/private rsa key pair.
	Enter file in which to save the key (/home/~~derek~~/.ssh/id_rsa):		Enter file in which to save the key (/home/username/.ssh/id_rsa):
	Created directory '/home/~~derek~~/.ssh'.		Created directory '/home/username/.ssh'.
	Your identification has been saved in /home/~~derek~~/.ssh/id_rsa.		Your identification has been saved in /home/username/.ssh/id_rsa.
	Your public key has been saved in /home/~~derek~~/.ssh/id_rsa.pub.		Your public key has been saved in /home/username/.ssh/id_rsa.pub.
	The key fingerprint is:		The key fingerprint is:
	ff:7a:99:28:fc:63:d6:10:44:4c:2e:68:76:44:76:7a ~~derek~~@localhost.localdomain		ff:7a:99:28:fc:63:d6:10:44:4c:2e:68:76:44:76:7a username@localhost.localdomain
	The key's randomart image is:		The key's randomart image is:
	+--[ RSA 2048]----+		+--[ RSA 2048]----+
Line 120:		Line 120:
	/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed		/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
	/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys		/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
	~~derek~~@localhost's password:		username@localhost's password:

	Number of key(s) added: 1		Number of key(s) added: 1
Line 168:		Line 168:
	Example: <pre>		Example: <pre>
	bash-4.2$ ssh-add -l		bash-4.2$ ssh-add -l
	2048 ee:83:10:c8:2f:2c:17:5e:ef:80:42:7e:ff:75:9e:53 /home/~~derek~~/.ssh/id_rsa (RSA)		2048 ee:83:10:c8:2f:2c:17:5e:ef:80:42:7e:ff:75:9e:53 /home/username/.ssh/id_rsa (RSA)
	</pre>		</pre>

Meganst at 18:08, 30 October 2020

2020-10-30T18:08:08Z

← Older revision		Revision as of 18:08, 30 October 2020
Line 151:		Line 151:

	<pre>		<pre>
	ssh-agent ~~[SHELL]~~		ssh-agent bash
	ssh-add -t [TIME]		ssh-add -t $TIME
	</pre>		</pre>

	~~You will need to specify a shell in this case <code>bash</code> but could be any shell as appropriate (<code>tcsh</code>, <code>sh</code>, etc).~~ The time specified by <code>-t</code> is specified in seconds.		The time specified by <code>-t</code> is specified in seconds.

	Example:		Example:

Mbaney at 15:34, 29 October 2020

2020-10-29T15:34:33Z

← Older revision		Revision as of 15:34, 29 October 2020
Line 6:		Line 6:
	#Determine your OS (and if Windows, what you will be using to create the key)		#Determine your OS (and if Windows, what you will be using to create the key)
	#*Windows		#*Windows
	#**Git ~~bash~~: follow instructions for Linux/MacOSX/Bash and Git Bash (for Windows)		#**Git Bash: follow instructions for Linux/MacOSX/Bash and Git Bash (for Windows)
	#**PuTTY: follow instructions for Windows (and PuTTY subsections)		#**PuTTY: follow instructions for Windows (and PuTTY subsections)
	#**TTSSH2: follow instructions for Windows (and TTSSH2 subsections)		#**TTSSH2: follow instructions for Windows (and TTSSH2 subsections)
Line 111:		Line 111:

	===Windows===		===Windows===
	For Windows hosts you can use [http://winscp.net/eng/download.php WinSCP] to copy the public key file onto a remote host. The root file system for the ~~bash subsystem~~ for ~~windows~~ is located under C:\Users\<username>\~~appdata~~\~~local~~\lxss\		For Windows hosts you can use [http://winscp.net/eng/download.php WinSCP] to copy the public key file onto a remote host. The root file system for the Bash Subsystem for Windows is located under C:\Users\username>\AppData\Local\lxss\

	===Linux/MacOSX/Bash and Git Bash (for Windows)===		===Linux/MacOSX/Bash and Git Bash (for Windows)===
Line 130:		Line 130:
	==Adding Keys to SSH Clients (Windows Only)==		==Adding Keys to SSH Clients (Windows Only)==
	;PuTTY		;PuTTY
	# Open ~~Putty~~ and enter the Fully Qualified Domain ~~name~~ for the host you wish to connect to		# Open PuTTY and enter the Fully Qualified Domain Name for the host you wish to connect to.
	# Go to the Connections tab on the side panel and click on the data subsection		# Go to the Connections tab on the side panel and click on the data subsection.
	# Under data enter your default user into the first box (Auto-login Username)		# Under data enter your default user into the first box. (Auto-login Username)
	# Go to the SSH section of the side panel and then go to the Auth Section		# Go to the SSH section of the side panel and then go to the Auth Section.
	# Under Auth click on the browse and navigate to the saved private key		# Under Auth click on the browse and navigate to the saved private key.
	# Go back to session on the side panel and save your settings by typing in a name in saved sessions pressing the save button		# Go back to session on the side panel and save your settings by typing in a name in saved sessions pressing the save button.
	;TTSSH2		;TTSSH2
	# Open the application		# Open the application.
	# Cancel the first box		# Cancel the first box.
	# Go to setup on the menu bar and go to SSH Authentication		# Go to setup on the menu bar and go to SSH Authentication.
	# Enter your username, Click on the option labeled "Use RSA ... key to log in", then use the private key button located next to this line to navigate to your private key file, and click Ok		# Enter your username, Click on the option labeled "Use RSA ... key to log in", then use the private key button located next to this line to navigate to your private key file, and click Ok.

	==Batch clusters==		==Batch clusters==
	Our [[SLURM]] clusters process jobs in batch and require the ability to ~~ssh~~ without entering a password. When creating a key for use with [[SLURM]], follow the above instructions for creating keys without passwords.		Our [[SLURM]] clusters process jobs in batch and require the ability to SSH without entering a password. When creating a key for use with [[SLURM]], follow the above instructions for creating keys without passwords.

	After creating this key pair please make sure you follow the [[SSH/Keys#Copy_the_public_key \| copy the public key]] instructions above to <code>localhost</code>. This will ensure that your key will be usable on all the cluster nodes since they have a shared home directory.		After creating this key pair please make sure you follow the [[SSH/Keys#Copy_the_public_key \| copy the public key]] instructions above to <code>localhost</code>. This will ensure that your key will be usable on all the cluster nodes since they have a shared home directory.

	==SSH Agents==		==SSH Agents==

	While it is very useful to protect your SSH key pair with a pass-phrase it can very time consuming to re-type the pass-phrase over and over. SSH provides a agent that runs in the background and allow you add a key(s) to it with a time limit that they will be unlocked for.		While it is very useful to protect your SSH key pair with a pass-phrase it can very time consuming to re-type the pass-phrase over and over. SSH provides a agent that runs in the background and allow you add a key(s) to it with a time limit that they will be unlocked for.

Line 165:		Line 164:
	</pre>		</pre>

	You will be prompted for your passphrase and, when entered correctly, you will be able to ~~ssh~~ without entering a password. You can check what keys are load when you are running inside a ssh-agent by using the command <code>ssh-add -l</code>.		You will be prompted for your passphrase and, when entered correctly, you will be able to SSH without entering a password. You can check what keys are load when you are running inside a ssh-agent by using the command <code>ssh-add -l</code>.

	Example: <pre>		Example: <pre>