Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

This article provides details and specifics for how to set up a Password-Free SSH key to connect to ARCC HPC Clusters from a Windows client.

...

Excerpt
nameWindows Specific Instructions
  1. Assuming the files you downloaded from OnDemand were placed in your Downloads folder (C:/Users/<your_username_on_the_PC>/Downloads in this example), go into your downloads folder and look for a file named with your uwyo username, and unzip that by right clicking and choosing “Extract All” Image Removed .

    Image Added

    This should create a new folder with your username.

  2. Check for a .ssh folder associated with your computer account. This should be located at C:/Users/<your_username_on_the_PC>/.ssh. (If your data is set to store on another drive, you may have a different drive letter in your path).

  3. If you do not have an .ssh folder under your Windows username, go to your start menu and search for command prompt. It should come up as a best match: Image Removed

    Image Added
  4. Once open, type in the following command into your command prompt: ssh-keygen
    then hit Enter/Return. This will generate a public/private rsa key pair (which we will be replacing) and create your .ssh folder with appropriate permissions structure.

  5. Copy the files from the extracted folder into your .ssh folder. You will be asked if it’s ok to replace the current files in the folder. Say ‘yes’ to confirm overwriting these files.

  6. Test your access with the new key files by opening a new command prompt window and ssh’ing to the HPC with the following command replacing <username> with your UWYO or ARCC HPC username and <clustername> with the HPC name: ssh <username>@<clustername>.arcc.uwyo.edu.
    (As an example: ssh cowboyjoe@beartooth.arcc.uwyo.edu)

  7. If the key is configured correctly, you will be logged into the cluster without having to enter your password or authenticate over 2 factor.

...

Expand
titleCorrecting SSH Key Permissions Issues using Windows GUI

The following instructions provide correction using Windows GUI interface.

  1. Disable permission inheritance for the .ssh folder

    1. Go up to the folder containing your key and certificate files. (Usually this is C:\Users\<your_username_on_the_computer>\)

    2. Right click on the .ssh folder (or whichever folder contains your new key files).

    3. Choose Properties from the list of options in the menu (you may also select the .ssh folder so it is highlighted and hit Alt+Enter)

    4. This will bring up a Properties window for your folder.

    5. Click on the Security tab in the window then click the Advanced button.

    6. This will bring up a new window for the folders Advanced Security Settings. Ensure that the Permissions tab is selected, then click the button to disable inheritance.

  2. Convert your directory/folder permissions to explicit permissions.

    1. You will be prompted for how to handle the blocked inheritance. Choose the option to Convert inherited permissions into explicit permissions on the object.
      Warning: Choosing the other option (to remove all inherited permissions from this object) can make the entire folder inaccessible. Do not select that option. If accidently selected, click the Cancel button at the bottom.

    2. After converting the inherited permissions to explicit permissions set them to remove all users except for SYSTEM and yourself. Ensure that both you and SYSTEM have Full Control under access:

    3. After confirming permissions for the folder are set correctly, Click the Apply button. Permissions should now be correctly set.

  3. Update permissions for the key files:

    1. Within the folder in which your key files are stored, perform the same actions to update permissions on each of the following files:

    2. id_ecdsa, id_ecsda.pub id_ecdsa-cert should all have the following permission properties:
      SYSTEM and your_username on the computer should have full control while no one else has access to them.