Changes between Version 62 and Version 63 of Documentation/bAccountManagement/DSSHConf


Ignore:
Timestamp:
Jun 21, 2018, 10:28:08 PM (6 years ago)
Author:
jkol
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Documentation/bAccountManagement/DSSHConf

    v62 v63  
    6565==== Configuring your SSH client ====
    6666  Under normal circumstances, as long as the private key file is located in the /home/your_username/.ssh/ folder, the command line SSH client will use the correct key when connecting.
    67  To test your setup, open a command-line terminal and (replacing your_orbit_username with your own ORBIT username) type:
     67 To test your setup, open a command-line terminal and (replacing ''your_orbit_username'' with your own ORBIT username) type:
    6868{{{
    6969ssh your_orbit_username@gw.orbit-lab.org
     
    160160==== Configuring your SSH client ====
    161161
    162  1. Open PuTTY
     162 1. Open PuTTY.
    163163
    164164 || [[Image(putty01.png, 250px)]] ||
    165165
    166  2. Navigate through the left side menu tree to "SSH" then "Auth"
     166 2. Navigate through the left side menu tree to "SSH" then "Auth".
    167167
    168168 || [[Image(putty02.png, 250px)]] ||
    169169
    170  3. Click the "Browse" button next to the "Private key file for authentication" field
     170 3. Click the "Browse" button next to the "Private key file for authentication" field.
    171171
    172172 || [[Image(putty03.png, 250px)]] ||
    173173
    174  4. Navigate through the left side menu tree back to "Session"
     174 4. Navigate to where you saved your '''private key file''' in the previous section and select it.
     175
     176 5. Navigate through the left side menu tree back to "Session".
    175177
    176178 || [[Image(putty04.png, 250px)]] ||
    177179
    178  5. Enter a name for this connection in the "Saved Sessions" field and click the "Save" button
     180 6. Enter a name for this connection in the "Saved Sessions" field and click the "Save" button.
    179181
    180182 || [[Image(putty05.png, 250px)]] ||
    181183
    182  6. Now any time you open PuTTY, select the session name you gave in the previous step and click "Load", this will load the private key file automatically (as long as you do not move it to a different folder on your computer).
     184 7. Now whenever you open PuTTY, select the session name you gave in the previous step and click "Load", this will load the private key file automatically so you do not have to repeat the prior steps each time (as long as you do not move it to a different folder on your computer).
    183185
    184186 || [[Image(putty06.png, 250px)]] ||
    185187
    186  7. Type {{{your_orbit_username@gw.orbit-lab.org}}} (replacing your_orbit_username with your own ORBIT username) into the "Host Name (or IP address)" field and click the "Open" button. You should be prompted to enter your key file passphrase and be able to successfully connect.
     188 8. Type {{{your_orbit_username@gw.orbit-lab.org}}} (replacing ''your_orbit_username'' with your own ORBIT username) into the "Host Name (or IP address)" field and click the "Open" button. You should be prompted to enter your key file passphrase and be able to successfully connect.
    187189
    188190 || [[Image(putty07.png, 250px)]] ||
     
    198200Are you sure you want to continue connecting (yes/no)?
    199201}}}
     202 OR
     203  || [[Image(putty_alert.png, 250px)]] ||
    200204 This is a normal message that occurs when your computer connects via SSH to another that it has never connected to before or if the "fingerprint" of the other machine changed (due to replacement or reconfiguration). Simply type {{{yes}}} and connection will proceed normally.
    201205[[BR]]