Ssh Keys - Revision history

Asherkin: Add note about PuTTY website.

2019-04-05T08:33:45Z

Add note about PuTTY website.

BAILOPAN: /* Windows */ - fixed permissions

2007-01-18T19:58:40Z

‎Windows: - fixed permissions

DS: Added some linkage back to the Subversion tutorial

2006-07-25T05:03:22Z

Added some linkage back to the Subversion tutorial

DS: /* Linux */ Shorter and sort of more consistent?

2006-07-08T22:11:43Z

‎Linux: Shorter and sort of more consistent?

DS: /* Linux */ Extra, read all about it

2006-07-07T02:27:18Z

‎Linux: Extra, read all about it

BAILOPAN: minor word usage changes

2006-07-07T02:17:40Z

minor word usage changes

BAILOPAN at 02:04, 7 July 2006

2006-07-07T02:04:10Z

DS: /* Windows */ The wonderful world of inconsistencies

2006-07-06T08:24:55Z

‎Windows: The wonderful world of inconsistencies

DS: /* Windows */ More minor formatting changes, part deux

2006-07-06T08:24:01Z

‎Windows: More minor formatting changes, part deux

DS: /* Linux */ Minor minor formatting changes

2006-07-06T08:22:25Z

‎Linux: Minor minor formatting changes

@@ Line 4: / Line 4: @@
 =Windows=
-First, you should make sure you have the <tt>Pageant</tt> and <tt>PuTTYGen</tt> programs downloaded. If you already have <tt>PuTTY</tt> and you installed it via an automated installer program, then it is likely you already have these. You should be able to find them in the directory in which <tt>PuTTY</tt> was installed. If you do not have them, you can grab both from the <tt>PuTTY</tt> [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html downloads] page.<br /><br />
+First, you should make sure you have the <tt>Pageant</tt> and <tt>PuTTYGen</tt> programs downloaded. If you already have <tt>PuTTY</tt> and you installed it via an automated installer program, then it is likely you already have these. You should be able to find them in the directory in which <tt>PuTTY</tt> was installed. If you do not have them, you can grab both from the <tt>PuTTY</tt> downloads page: https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html. There are lots of websites, many more legitimate looking than the official site, distributing malicious copies of the <tt>PuTTY</tt> tools due to its popularity, make sure to always download from the official website linked previously.<br /><br />
 Open <tt>PuTTYGen</tt> first and click the button labeled "Generate." It will then ask you to move the mouse cursor over the blank area on the program's window (in order to generate some randomness for the keys). Then it will ask you to enter a comment (which is already filled, but may be changed) and the key's passphrase twice. You may leave this passphrase blank if you never wish to enter any kind of password for accessing the server via SSH. However it might be a good idea to enter something there for extra security. When using <tt>Pageant</tt>, you will only have to enter this passphrase once per Windows login. Your <tt>PuTTYGen</tt> window may look like this:

@@ Line 18: / Line 18: @@
 Now you can go into this directory and type <tt>echo</tt>. Then right click on your terminal window. This should then paste your public key into the window. Then type a space after your public key followed by <tt>>> authorized_keys</tt> and press the enter key. Here is an example:
 <pre>echo mypastedkey >> authorized_keys</pre>
 Now you should open <tt>Pageant</tt>. An icon for the program should appear in your system tray. Right click on this icon and select "Add Key" from the context menu.

@@ Line 25: / Line 25: @@
 A file dialog box will appear. Find and select the private key file that you saved earlier. If you chose to use a passphrase, it will ask you to enter it once. If you did not have a passphrase, then the key will be added automatically.
-Now you may access the server via SSH in any way (such as using TortoiseSVN) without having to enter a password again. If you reboot your computer, or log out of your Windows session and log back in, you only have to open <tt>Pageant</tt> and add your key file again.
+Now you may access the server via SSH in any way (such as using [[Subversion Tutorial#TortoiseSVN|TortoiseSVN]]) without having to enter a password again. If you reboot your computer, or log out of your Windows session and log back in, you only have to open <tt>Pageant</tt> and add your key file again.
 =Linux=
@@ Line 61: / Line 61: @@
 <pre>echo killall ssh-agent >> ~/.bash_logout</pre>
-You may now access the remote server via SSH in any way (such as using svn) without having to enter a password again. If you reboot or log out and log back in, you only have to run <tt>ssh-agent</tt> and <tt>ssh-add</tt> again.
+You may now access the remote server via SSH in any way (such as using [[Subversion Tutorial|svn]]) without having to enter a password again. If you reboot or log out and log back in, you only have to run <tt>ssh-agent</tt> and <tt>ssh-add</tt> again.

@@ Line 45: / Line 45: @@
 Here is an example of the above information:
-<pre>scp /home/users/damagedsoul/.ssh/id_rsa.pub damagedsoul@takkun.tcwonline.org:~/
+<pre>scp ~/.ssh/id_rsa.pub damagedsoul@takkun.tcwonline.org:~/
 ssh damagedsoul@takkun.tcwonline.org</pre>
 These next commands are then executed on the remote server:

@@ Line 29: / Line 29: @@
 =Linux=
-First, a private-public key pair must be created. You can do this by using <tt>ssh-keygen</tt>, which comes with openssh (which should already be installed). Type "<tt>ssh-keygen -t rsa</tt>". You will be asked to type a path to the file that will be created. You can press enter here because the default is usually fine. You will then be asked for the passphrase twice. As mentioned in the Windows section above, this is optional. You may leave this passphrase blank (by pressing enter when it asks) if you wish to use the keys without having to type a password. However, it might be a good idea to use one for security. When using <tt>ssh-agent</tt>, you will only have to enter this passphrase once per login.
+First, a private-public key pair must be created. You can do this by using <tt>ssh-keygen</tt>, which comes with openssh (which should already be installed). Type "<tt>ssh-keygen -t rsa</tt>". You will be asked to type a path to the file that will be created. You can press enter here because the default is usually fine. You will then be asked for the passphrase twice. As mentioned in the Windows section above, this is optional. You may leave this passphrase blank (by pressing enter when it asks) if you wish to use the keys without having to type a password. However, it might be a good idea to use one for extra security. When using <tt>ssh-agent</tt>, you will only have to enter this passphrase once per login.
 Here's an example of what may occur with <tt>ssh-keygen</tt>:

@@ Line 1: / Line 1: @@
 =Introduction=
-A private-public key pair allows one to a access remote server via SSH via a preset encryption key.  Key pairs can be generated with <tt>ssh-keygen</tt> on Linux and <tt>PuTTYGen</tt> on Windows.  When a key pair is generated, a passphrase may be created.  If there is a passphrase set, then <tt>ssh-agent</tt> on Linux or <tt>Pageant</tt> on Windows can be used for logging in without needing to type a passphrase. This article explains how to use these tools in order to log in to a remote server using SSH and not typing a password.
+A private-public key pair allows one to a access remote server via SSH with a preset encryption key, rather than just a password.  Key pairs can be generated with <tt>ssh-keygen</tt> on Linux and <tt>PuTTYGen</tt> on Windows.  When a key pair is generated, a passphrase may be created.  If there is a passphrase set, then <tt>ssh-agent</tt> on Linux or <tt>Pageant</tt> on Windows can be used for logging in without needing to type the passphrase. This article explains how to use these tools in order to log in to a remote server using SSH and not typing a password.
 =Windows=
-First you should make sure you have two programs named <tt>Pageant</tt> and <tt>PuTTYGen</tt>. If you already have a program called <tt>PuTTY</tt> and you installed it via an automated installer program, then it is likely you already have these. You should be able to find them in the directory in which <tt>PuTTY</tt> was installed. If you do not have these, you can grab them both from the <tt>PuTTY</tt> [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html downloads] page.<br /><br />
+First, you should make sure you have the <tt>Pageant</tt> and <tt>PuTTYGen</tt> programs downloaded. If you already have <tt>PuTTY</tt> and you installed it via an automated installer program, then it is likely you already have these. You should be able to find them in the directory in which <tt>PuTTY</tt> was installed. If you do not have them, you can grab both from the <tt>PuTTY</tt> [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html downloads] page.<br /><br />
-Open <tt>PuTTYGen</tt> first and click the button labeled "Generate." It will then ask you to move the mouse cursor over the blank area on the program's window in order to generate some randomness for the keys. Then it will ask you to enter a comment (which is already filled, but may be changed) and the key's passphrase twice. You may leave this passphrase blank if you never wish to enter any kind of password for accessing the server via SSH. However it might be a good idea to enter something there for the sake of security. When using <tt>Pageant</tt>, you will only have to enter this passphrase once per Windows login. Your <tt>PuTTYGen</tt> window may look like this:
+Open <tt>PuTTYGen</tt> first and click the button labeled "Generate." It will then ask you to move the mouse cursor over the blank area on the program's window (in order to generate some randomness for the keys). Then it will ask you to enter a comment (which is already filled, but may be changed) and the key's passphrase twice. You may leave this passphrase blank if you never wish to enter any kind of password for accessing the server via SSH. However it might be a good idea to enter something there for extra security. When using <tt>Pageant</tt>, you will only have to enter this passphrase once per Windows login. Your <tt>PuTTYGen</tt> window may look like this:
 [[Image:PuTTYGen.png]]
@@ Line 12: / Line 12: @@
 Click the button labeled "Save private key" and save this key somewhere on your computer, such as your <tt>My Documents</tt> directory. Right click in the area that shows your public key and select "Select All" from the menu. Then right click again and select "Copy."
-Next, open a terminal window (with <tt>PuTTY</tt> or some other program) to the server that you wish to access with this key pair. Navigate to your home directory if you are not already there and look for a directory named <tt>.ssh</tt>. If you do not have this directory, then create it like so:
+Next, open a terminal window (with <tt>PuTTY</tt> or some other program) to the server that you wish to access using this key pair. Navigate to your home directory if you are not already there, and look for a directory named <tt>.ssh</tt>. If you do not have this directory, then create it like so:
 <pre>cd ~
-mkdir --mode=700 .ssh</pre>
+mkdir --mode=700 .ssh
-Go into this directory and type <tt>echo</tt>. Then right click on your terminal window. This should then paste your public key into the window. Then type a space after your public key followed by <tt>>> authorized_keys</tt> and press the enter key. Here is an example:
+cd .ssh</pre>
 <pre>echo mypastedkey >> authorized_keys</pre>
@@ Line 22: / Line 23: @@
 [[Image:Pageant_TrayMenu.png]]
-A file dialog box will appear. Find and select the private key file that you saved earlier. If you entered a passphrase earlier, it will ask you to enter it once. If you did not have a passphrase, then the key will be added without any more dialogs.
+A file dialog box will appear. Find and select the private key file that you saved earlier. If you chose to use a passphrase, it will ask you to enter it once. If you did not have a passphrase, then the key will be added automatically.
-Now you may access the server via SSH in any way (such as using TortoiseSVN) without having to enter a password again. If you reboot your computer or log out of your Windows session and log back in, you only have to open <tt>Pageant</tt> again and add the private key file.
+Now you may access the server via SSH in any way (such as using TortoiseSVN) without having to enter a password again. If you reboot your computer, or log out of your Windows session and log back in, you only have to open <tt>Pageant</tt> and add your key file again.
 =Linux=
-First a private-public key pair must be. You can do that by using <tt>ssh-keygen</tt> which comes with openssh which should already be installed. Type "ssh-keygen -t rsa" and press the enter key. You will be asked to type a path to the file that will be created. You can press enter here because the default is usually fine. Then you will be asked for the passphrase twice. As mentioned in the Windows section above, this is optional. You may leave this passphrase blank (by pressing enter when it asks) if you never wish to enter any kind of password for accessing the server via SSH. However it might be a good idea to enter something there for the sake of security. When using <tt>ssh-agent</tt>, you will only have to enter this passphrase once per login.
+First, a private-public key pair must be created. You can do this by using <tt>ssh-keygen</tt>, which comes with openssh (which should already be installed). Type "<tt>ssh-keygen -t rsa</tt>". You will be asked to type a path to the file that will be created. You can press enter here because the default is usually fine. You will then be asked for the passphrase twice. As mentioned in the Windows section above, this is optional. You may leave this passphrase blank (by pressing enter when it asks) if you wish to use the keys without having to type a password. However, it might be a good idea to use one for security. When using <tt>ssh-agent</tt>, you will only have to enter this passphrase once per login.
 Here's an example of what may occur with <tt>ssh-keygen</tt>:
@@ Line 51: / Line 52: @@
 cat id_rsa.pub >> .ssh/authorized_keys</pre>
-Now exit from the remote server's SSH session. You now need to run <tt>ssh-agent</tt>. However, if you have a blank passphrase, the following steps are not even necessary and you may begin logging in to the remote server without a password.
+Now exit from the remote server's SSH session. You now need to run <tt>ssh-agent</tt>. However, if you have a blank passphrase, the following steps are not necessary and you may begin logging in to the remote server without a password.
-But if you did enter a passphrase, then execute the following commands:
+If you did enter a passphrase, then execute the following commands:
 <pre>eval `ssh-agent -s`
 ssh-add</pre>

← Older revision		Revision as of 02:04, 7 July 2006
Line 1:		Line 1:
	=Introduction=		=Introduction=
−	A private-public key pair allows one to a access remote server via SSH ~~by only typing~~ a ~~passphrase~~. Key pairs can be generated with <tt>ssh-keygen</tt> on Linux and <tt>PuTTYGen</tt> on Windows. When a key pair is generated, a passphrase ~~must~~ be created. ~~The passphrase can be blank. But if~~ there is a passphrase set, then <tt>ssh-agent</tt> on Linux or <tt>Pageant</tt> on Windows can be used for logging in without needing to type a passphrase. This article explains how to use these tools in order to log in to a remote server using SSH and not typing a password.	+	A private-public key pair allows one to a access remote server via SSH via a preset encryption key. Key pairs can be generated with <tt>ssh-keygen</tt> on Linux and <tt>PuTTYGen</tt> on Windows. When a key pair is generated, a passphrase may be created. If there is a passphrase set, then <tt>ssh-agent</tt> on Linux or <tt>Pageant</tt> on Windows can be used for logging in without needing to type a passphrase. This article explains how to use these tools in order to log in to a remote server using SSH and not typing a password.

@@ Line 42: / Line 42: @@
 :11:bb:1f:9b:e4:52:53:e1:75:30:75:b5:d2:c1:ba damagedsoul@sente.tcwonline.org</pre>
-There should now be a file named <tt>id_rsa.pub</tt> in the <tt>.ssh</tt> directory of your home directory. Upload this file to the home directory of the server you wish to access using scp or some other means. Start an SSH session with the remote server and then navigate to your home directory if you are not already there. Then you can add the contents of id_rsa.pub to your authorized_keys file in the <tt>.ssh</tt> directory. If you do not have an <tt>.ssh</tt> directory, then you will have to create it.
+There should now be a file named <tt>id_rsa.pub</tt> in the <tt>.ssh</tt> directory of your home directory. Upload this file to the home directory of the server you wish to access using <tt>scp</tt> or some other means. Start an SSH session with the remote server and then navigate to your home directory if you are not already there. Then you can add the contents of <tt>id_rsa.pub</tt> to your <tt>authorized_keys</tt> file in the <tt>.ssh</tt> directory. If you do not have an <tt>.ssh</tt> directory, then you will have to create it.
 Here is an example of the above information: