{"id":30959,"date":"2025-03-25T09:39:51","date_gmt":"2025-03-25T13:39:51","guid":{"rendered":"https:\/\/www.uvm.edu\/it\/kb\/?post_type=ht_kb&p=30959"},"modified":"2026-02-23T14:37:22","modified_gmt":"2026-02-23T19:37:22","slug":"ssh-keys","status":"publish","type":"ht_kb","link":"https:\/\/www.uvm.edu\/it\/kb\/article\/ssh-keys\/","title":{"rendered":"SSH Keys"},"content":{"rendered":"

\"\"<\/a>SSH keys are an alternative method of authentication, using pre-generated key files in place of a password. This method also currently removes the requirement for Duo multifactor authentication. This article outlines how to generate a key pair, where to save them, and which services will accept SSH key pairs as an authentication method.<\/span><\/p>\n

Generate a key pair<\/h2>\n

Before authenticating with an SSH key pair, you must generate one. There are several methods you can use to accomplish this, and the process varies depending on the operating system of your device and the software you’re using to connect.<\/p>\n

Windows<\/h3>\n \t\t
\r\n \t\t\t

ssh-keygen (Windows Terminal)<\/h3><\/div>\r\n \t\t\t
\r\n \t\t\t\t
\r\n \t\t\t\t\t<\/p>\n
    \n
  1. Open a Windows PowerShell<\/strong> window. One way to do this is expand the Start Menu (<\/i><\/strong>), type “PowerShell<\/strong>“, and click the Best Match<\/strong> result that appears.
    \n\"Windows<\/a><\/li>\n
  2. Type “ssh-keygen<\/strong>” and hit Enter<\/strong> on your keyboard.\n
    ssh-keygen<\/pre>\n<\/li>\n
  3. Type in the path to a location and filename to save the private key, or just hit Enter<\/strong> to stick with the default (recommended).
    \n    \"Windows<\/a><\/li>\n
  4. Choose a passphrase<\/strong> that you’ll have to enter each time you use this key pair and enter the same passphrase again to confirm, hitting Enter<\/strong> on your keyboard after each time. Or, just hit Enter twice without typing anything<\/em> to bypass passphrase entry (recommended).\n
    \n    \t\t\tKey Fingerprints<\/span>    \t\t\t    \t\t\t\t<\/p>\n
    \n    \t\t\t\t\tAfter generating the key pair, you’ll receive some text known as a key fingerprint<\/strong>. I would recommend ignoring that text as well as the randomart image <\/strong>that follows for now. See the end of this article for more information about fingerprints and verifying host keys<\/a>.    \t\t\t\t<\/p>\n<\/p><\/div>\n
    \n    \t\t<\/li>\n
  5. The new key pair can be found in your local .ssh<\/strong> folder or whichever location you chose in Step 3<\/em> above. The .ssh folder is a hidden subfolder of your Windows User folder. See these instructions for more info about hidden folders in Windows<\/a>.
    \n    \"Windows<\/a><\/li>\n<\/ol>\n
    \n    \t\t\t\t<\/div>\r\n    \t\t\t<\/div>\r\n    \t\t<\/div>\r\n    \t\t\n    \t\t
    \r\n    \t\t\t
    WinSCP<\/h3><\/div>\r\n    \t\t\t
    \r\n    \t\t\t\t
    \r\n    \t\t\t\t\t<\/p>\n
    WinSCP does not come preinstalled, but can be installed for free by visiting their website<\/a>.<\/p>\n
      \n
    1. Open the WinSCP app, click New Tab<\/strong>, enter the Host name<\/strong> of the remote server and your NetID<\/strong>, and then click Advanced<\/strong>.
      \n      \"WinSCP<\/a><\/li>\n
    2. From the SSH<\/strong> > Authentication<\/strong> tab, expand the Tools<\/strong> drop-down menu, and click Generate New Key Pair with PuTTYgen…<\/strong>.
      \n      \"WinSCP<\/a><\/li>\n
    3. Click Generate<\/strong>. Then, to fill the green progress bar and advance to the next step, move your mouse around the blank area.
      \n      \"PuTTY<\/a><\/p>\n
      \n    \t\t\tKey Fingerprints<\/span>    \t\t\t    \t\t\t\t<\/p>\n
      \n    \t\t\t\t\tAfter generating the key pair, you’ll receive some text known as a key fingerprint<\/strong>. I would recommend ignoring that text for now. See the end of this article for more information about fingerprints and verifying host keys<\/a>.    \t\t\t\t<\/p>\n<\/p><\/div>\n
      \n    \t\t<\/li>\n
    4. Click Save public key<\/strong>, choose a File name<\/strong>, and click Save<\/strong>. Do the same for private key<\/strong>. Names like “silk_key_pub” and “silk_key_priv”, accordingly, would work. In my testing, the default save location was my .ssh<\/strong> folder, which is the recommended location, but any location on your computer. Click Yes<\/strong> if warned about passphrase.<\/li>\n
    5. Close the PuTTY Key Generator<\/strong> window.<\/li>\n
    6. Expand the Tools<\/strong> drop-down menu once more and click Install Public Key into Server…<\/strong>.<\/li>\n
    7. The window that appears filters the visible files by Private Key<\/strong>, which doesn’t make sense because we are looking for a Public<\/em> key right now. Expand the drop-down menu in the bottom-right corner of the window and select All Files (*.*)<\/strong>.
      \n      \"Windows<\/a><\/li>\n
    8. Select the public key you saved above (“silk_key_pub<\/strong>” in my example) and click Open<\/strong>.
      \n      \"Windows<\/a><\/li>\n
    9. Enter your NetID password and hit Enter.<\/li>\n
    10. You are now ready to connect to the specified server using your new key pair.<\/li>\n<\/ol>\n
      \n    \t\t\t\t<\/div>\r\n    \t\t\t<\/div>\r\n    \t\t<\/div>\r\n    \t\t\n    \t\t
      \r\n    \t\t\t
      PuTTYgen<\/h3><\/div>\r\n    \t\t\t
      \r\n    \t\t\t\t
      \r\n    \t\t\t\t\t<\/p>\n
      PuTTY Key Generator (PuTTYgen) does not come pre-installed on Windows, but comes bundled with PuTTY, which can be installed from the UVM Software Portal<\/a>.<\/p>\n
        \n
      1. Open the PuTTY Key Generator.\u00a0One way to do this is expand the Start Menu (<\/i><\/strong>), type “PuTTYgen<\/strong>“, and click the Best match<\/strong> result that appears.
        \n        \"Windows<\/a><\/li>\n
      2. Click Generate<\/strong>. Then, to fill the green progress bar and advance to the next step, move your mouse around the blank area.
        \n        \"PuTTY<\/a><\/p>\n
        \n    \t\t\tKey Fingerprints<\/span>    \t\t\t    \t\t\t\t<\/p>\n
        \n    \t\t\t\t\tAfter generating the key pair, you’ll receive some text known as a key fingerprint<\/strong>. I would recommend ignoring that text for now. See the end of this article for more information about fingerprints and verifying host keys<\/a>.    \t\t\t\t<\/p>\n<\/p><\/div>\n
        \n    \t\t<\/li>\n
      3. Click Save public key<\/strong>, choose a File name<\/strong>, and click Save<\/strong>.\u00a0Names like “silk_key_pub” and “silk_key_priv”, accordingly, would work. In my testing, the default save location was my .ssh<\/strong> folder, which is the recommended location, but any location on your computer or OneDrive is fine. Click Yes<\/strong> if warned about passphrase.\u00a0Do the same for private key<\/strong>.<\/li>\n<\/ol>\n
        \n    \t\t\t\t<\/div>\r\n    \t\t\t<\/div>\r\n    \t\t<\/div>\r\n    \t\t\n
        macOS and Linux<\/h3>\n    \t\t
        \r\n    \t\t\t
        ssh-keygen (Terminal\/Shell)<\/h3><\/div>\r\n    \t\t\t
        \r\n    \t\t\t\t
        \r\n    \t\t\t\t\t<\/p>\n
          \n
        1. Open the Terminal<\/strong> app. One way to do this is expand the Spotlight Search (<\/i><\/strong>) or Launcher, type “Terminal<\/strong>“, and then hit Return<\/strong> or Enter<\/strong> on your keyboard.
          \n\"Linux<\/a><\/li>\n
        2. Type “ssh-keygen<\/strong>” and hit Return<\/strong> or Enter<\/strong> on your keyboard.\n
          ssh-keygen<\/pre>\n<\/li>\n
        3. Type in the path to a location and filename to save the private key, or just hit Return<\/strong> or Enter<\/strong> to stick with the default (recommended).
          \n          \"macOS<\/a><\/li>\n
        4. Optionally, choose a passphrase<\/strong> that you’ll have to enter each time you use this key pair and enter the same passphrase again to confirm, hitting Enter<\/strong> on your keyboard after each time. Or, just hit Enter twice without typing anything<\/em> to bypass passphrase entry (recommended).\n
          \n    \t\t\tKey Fingerprints<\/span>    \t\t\t    \t\t\t\t<\/p>\n
          \n    \t\t\t\t\tAfter generating the key pair, you’ll receive some text known as a key fingerprint<\/strong>. I would recommend ignoring that text for now. See the end of this article for more information about fingerprints and verifying host keys<\/a>.    \t\t\t\t<\/p>\n<\/p><\/div>\n
          \n    \t\t<\/li>\n
        5. The new key pair can be found in your local .ssh<\/strong> folder or whichever location you chose in Step 3<\/em> above. The public key has the .pub<\/strong> file extension and the private key has no file extension. The .ssh folder is a hidden subfolder of your macOS User folder. See these instructions for more info about hidden folders in macOS<\/a>.
          \n          \"macOS<\/a><\/li>\n<\/ol>\n
          \n    \t\t\t\t<\/div>\r\n    \t\t\t<\/div>\r\n    \t\t<\/div>\r\n    \t\t\n
          Add key pair to remote server or service<\/h2>\n    \t\t
          \r\n    \t\t\t
          GitLab<\/h3><\/div>\r\n    \t\t\t
          \r\n    \t\t\t\t
          \r\n    \t\t\t\t\t<\/p>\n
            \n
          1. Copy the contents of your public key file to the clipboard. One way to do this is to navigate to your .ssh folder, open the file you saved above ending in .pub in a text editor, select all the contents, right-click the highlighted text, and click Copy<\/strong>.<\/li>\n
          2. Sign in to UVM’s GitLab<\/a> with your NetID and password.<\/li>\n
          3. Expand the sidebar, click your avatar, and select Edit profile<\/strong>.
            \n            \"GitLab<\/a><\/li>\n
          4. Expand the sidebar again and click SSH Keys<\/a><\/strong>.<\/li>\n
          5. Click Add new key<\/strong>.<\/li>\n
          6. Paste the contents of the public key file into the Key<\/strong> field.<\/li>\n
          7. Choose a Title<\/strong> for this key that indicates which device this key is for, like the example shown, “MacBook key”.\n
            \n    \t\t\tOne key pair per computer<\/span>    \t\t\t    \t\t\t\t<\/p>\n
            \n    \t\t\t\t\tA key pair is designed to work from one computer; to connect from another computer, generate a new pair. Once generated and saved to your local machine, the public key can be added to any or all of the UVM services and servers mentioned here.    \t\t\t\t<\/p>\n<\/p><\/div>\n
            \n    \t\t<\/li>\n
          8. Optionally, remove or change the Expiration date<\/strong>.<\/li>\n
          9. Click Add key<\/strong>.<\/li>\n
          10. Once your public key has been safely saved remotely, it is a good idea to delete or move the local copy of the public key file. Your private key and public key should not be stored to the same location.<\/li>\n<\/ol>\n
            \n    \t\t\t\t<\/div>\r\n    \t\t\t<\/div>\r\n    \t\t<\/div>\r\n    \t\t\n    \t\t
            \r\n    \t\t\t
            Silk, Zoo, VACC, and more<\/h3><\/div>\r\n    \t\t\t
            \r\n    \t\t\t\t
            \r\n    \t\t\t\t\t<\/p>\n
              \n
            1. Copy the contents of your public key file to the clipboard. One way to do this is to navigate to your .ssh folder, open the file you save above ending in .pub in a text editor, select all the contents, right-click the highlighted text, and click Copy<\/strong>.<\/li>\n
            2. Connect to the server with your NetID and password. Here is a non-exhaustive list of servers this will work with:\n
                \n
              1. Silk<\/a><\/li>\n
              2. Zoo<\/a><\/li>\n
              3. Zebra<\/a><\/li>\n
              4. Linux Research VMs<\/a><\/li>\n
              5. VACC<\/a><\/li>\n<\/ol>\n<\/li>\n
              6. Navigate to your .ssh<\/strong> folder. If it doesn’t exist, create one. Folders with names beginning with periods are hidden by default. Click here for more info about hidden files<\/a>.<\/li>\n
              7. Open the authorized_keys<\/strong> file in a text editor. If it doesn’t exist, create one. The name should be exactly “authorized_keys” with no file extension at the end, and an underscore (“_<\/strong>“) in the middle.<\/li>\n
              8. On a new line, paste<\/strong> the contents of the public key file, and save<\/strong> authorized_keys.<\/li>\n
              9. Once your public key has been safely saved remotely, it is a good idea to delete or move the local copy of the public key file. Your private key and public key should not be stored to the same location.<\/li>\n<\/ol>\n
                \n    \t\t\t\t<\/div>\r\n    \t\t\t<\/div>\r\n    \t\t<\/div>\r\n    \t\t\n
                Connect<\/h2>\n    \t\t
                \r\n    \t\t\t
                SSH (Terminal commands)<\/h3><\/div>\r\n    \t\t\t
                \r\n    \t\t\t\t
                \r\n    \t\t\t\t\t<\/p>\n
                Secure Shell (SSH) is a method of connecting to a remote Linux or Unix system via a command line interface like the Terminal app. While the origins of the terms are related, it should not be confused with “SSH Keys<\/em>” (in this context).<\/p>\n
                The SSH command also happens to be the easiest way to verify if your SSH keys are set up correctly. More information about that can be found here<\/a>.<\/p>\n
                  \n
                1. Open a Terminal<\/strong> window.<\/li>\n
                2. Enter SSH<\/strong> followed by a space, your NetID<\/strong>, an @<\/strong> symbol, and the hostname<\/strong> of the server you’re connecting to, like this:\n
                   ssh netid@host.uvm.edu<\/pre>\n
                  Replace “netid” with your own NetID, and “host” with the name of the server, like “zoo” for Zoofiles or “w3” for Silk.<\/li>\n
                3. Hit Enter<\/strong>. If your SSH keys are set up properly you’ll be connected to the remote server via the command line interface without the need to enter a password.<\/li>\n<\/ol>\n
                  \n    \t\t\t\t<\/div>\r\n    \t\t\t<\/div>\r\n    \t\t<\/div>\r\n    \t\t\n    \t\t
                  \r\n    \t\t\t
                  Git<\/h3><\/div>\r\n    \t\t\t
                  \r\n    \t\t\t\t
                  \r\n    \t\t\t\t\t<\/p>\n
                  Git may not come pre-installed on your system, but can be installed for free using these instructions on git-scm.com<\/a>. To check if git is installed, you can run the “git –version” command from a Terminal window.<\/p>\n
                  To verify that your SSH key pair is set up correctly to connect to GitLab using Git, see these “Verify that you can connect” instructions from gitlab.com<\/a>.<\/p>\n
                  For more help using Git to connect to GitLab, see these general instructions from gitlab.com<\/a>.<\/p>\n
                  \n    \t\t\t\t<\/div>\r\n    \t\t\t<\/div>\r\n    \t\t<\/div>\r\n    \t\t\n    \t\t
                  \r\n    \t\t\t
                  Windows Terminal Profile<\/h3><\/div>\r\n    \t\t\t
                  \r\n    \t\t\t\t
                  \r\n    \t\t\t\t\t<\/p>\n
                  If you use text-based commands from a Windows computer to connect to the same server all the time, you can save yourself some typing and set up a profile ahead of time. To get started, see the SSH in Windows Terminal tutorial on microsoft.com<\/a>.<\/p>\n
                  \n    \t\t\t\t<\/div>\r\n    \t\t\t<\/div>\r\n    \t\t<\/div>\r\n    \t\t\n    \t\t
                  \r\n    \t\t\t
                  FileZilla<\/h3><\/div>\r\n    \t\t\t
                  \r\n    \t\t\t\t
                  \r\n    \t\t\t\t\t<\/p>\n
                  FileZilla is free software that can be installed by visiting their website directly<\/a>. However, a link to FileZilla can be found on the UVM Software Portal<\/a> as well.<\/p>\n
                    \n
                  1. Open the Edit<\/strong> menu (on macOS, it’s the FileZilla<\/strong> menu instead) at the top of the main FileZilla menu and click Settings…<\/strong>.<\/li>\n
                  2. Expand the Connection<\/strong> > SFTP<\/strong> tab and click Add key file…<\/strong>.
                    \n                    \"FileZilla<\/a><\/li>\n
                  3. Navigate to the folder containing your private key. It may not have the same name as the file in the example below, but it will be the one generated above with no<\/em> file extension. Select the file and click Open<\/strong>.
                    \n                    \"FileZilla<\/a><\/li>\n
                  4. Click OK<\/strong> to close the settings window.<\/li>\n
                  5. Enter the Host <\/strong>(w3.uvm.edu for example), Username <\/strong>(your NetID), and Port <\/strong>(Likely “22”), but leave the Password field blank, and click Quickconnect<\/strong>.<\/li>\n<\/ol>\n
                    \n    \t\t\t\t<\/div>\r\n    \t\t\t<\/div>\r\n    \t\t<\/div>\r\n    \t\t\n    \t\t
                    \r\n    \t\t\t
                    WinSCP<\/h3><\/div>\r\n    \t\t\t
                    \r\n    \t\t\t\t
                    \r\n    \t\t\t\t\t<\/p>\n
                    WinSCP is free software that can be installed by visiting winscp.net<\/a>. WinSCP has much of the same functionality as FileZilla, and is only available for Windows, but it is an option especially for users who are already comfortable with its interface.<\/p>\n
                    One advantage of WinSCP is its built-in methods for generating a key pair and installing the public key on the server. If you followed those steps when you generated the key pair using the WinSCP method above, you can skip this section. However, it is still possible to add a key generated with a different method using these steps:<\/p>\n
                      \n
                    1. Open the WinSCP app, click New Tab<\/strong>, enter the Host name<\/strong> of the remote server and your NetID<\/strong>, and then click Advanced<\/strong>.
                      \n                      \"WinSCP<\/a><\/li>\n
                    2. From the SSH<\/strong> > Authentication<\/strong> tab, click the ellipsis (<\/i><\/strong>) button to the right of the Private key file<\/strong> field.
                      \n                      \"WinSCP<\/a><\/li>\n
                    3. The window that appears filters the visible files by the .ppk<\/strong> file extension, which may not work depending on the method used to generate the key. If you’re in the correct folder, but the file is not shown, expand the drop-down menu in the bottom-right corner of the window and select All Files (*.*)<\/strong>.
                      \n                      \"Windows<\/a><\/li>\n
                    4. Navigate to the folder containing your private key. It may not have the same name as the file in the example below, but it will either have no<\/em> file extension or<\/em> the extension “.ppk<\/strong>“. Select the file and click Open<\/strong>.
                      \n                      \"WinSCP<\/a><\/li>\n
                    5. If a Confirm<\/strong> window appears, click OK\u00a0<\/strong>and then Save <\/strong>and then OK<\/strong> again.
                      \n                      \"WinSCP<\/a><\/li>\n
                    6. Click OK<\/strong> to close the Settings window.<\/li>\n
                    7. Click Login<\/strong>. If you receive an unknown server warning, see the end of this article for more information about fingerprints and verifying host keys, or just click Accept<\/strong>. You can tell it worked if you successfully connect to the remote server without entering your NetID password.<\/li>\n<\/ol>\n
                      \n    \t\t\t\t<\/div>\r\n    \t\t\t<\/div>\r\n    \t\t<\/div>\r\n    \t\t\n    \t\t
                      \r\n    \t\t\t
                      Fetch<\/h3><\/div>\r\n    \t\t\t
                      \r\n    \t\t\t\t
                      \r\n    \t\t\t\t\t<\/p>\n
                      \n    \t\t\tDoesn't work on newest version of app<\/span>    \t\t\t    \t\t\t\t<\/p>\n
                      \n    \t\t\t\t\tFetch provides instructions to connect to a remote server using an SSH key pair<\/a>, but they do not appear to work on the latest version of the Fetch app. I’m hoping they will fix this soon. For now, I would recommend the FileZilla app<\/a> instead. Fetch can still be used to connect to UVM servers, but only using Duo Multi-Factor Authentication<\/a>, and only using your default authentication method.    \t\t\t\t<\/p>\n<\/p><\/div>\n
                      \n    \t\t<\/p>\n
                      Fetch can be installed by visiting the\u00a0UVM Software Portal<\/a> but is available for macOS only.<\/p>\n
                      \n    \t\t\t\t<\/div>\r\n    \t\t\t<\/div>\r\n    \t\t<\/div>\r\n    \t\t\n    \t\t
                      \r\n    \t\t\t
                      PuTTY<\/h3><\/div>\r\n    \t\t\t
                      \r\n    \t\t\t\t
                      \r\n    \t\t\t\t\t<\/p>\n
                      PuTTY is free software for Windows PCs only that can be installed by visiting putty.org<\/a>. A link to PuTTY can be found on the UVM Software Portal<\/a> as well. PuTTY has much of the same functionality as the SSH Terminal Command method outlined above, but it is an option especially for users who are already more comfortable with its graphical Configuration interface.<\/p>\n
                        \n
                      1. Open the PuTTY app. The PuTTY Configuration<\/strong> window will appear.<\/li>\n
                      2. If you haven’t previously saved a session, enter the Host Name<\/strong> of the server you’re connecting to (“w3.uvm.edu” for example) and the Port <\/strong>(likely “22”). Then, expand Connection<\/strong>, SSH<\/strong>, and Auth<\/strong>, and select Credentials<\/strong>.
                        \n                        \"PuTTY<\/a><\/li>\n
                      3. Click Browse…<\/strong> to the right of the Private key file for authentication<\/strong> field.<\/li>\n
                      4. The window that appears filters the visible files by the .ppk<\/strong> file extension, which may not work depending on the method used to generate the key. If you’re in the correct folder, but the file is not shown, expand the drop-down menu in the bottom-right corner of the window and select All Files (*.*)<\/strong>.
                        \n                        \"Windows<\/a><\/li>\n
                      5. Navigate to the folder containing your private key. It may not have the same name as the file in the example below, but it will either have no<\/em> file extension or<\/em> the extension “.ppk<\/strong>“. Select the file and click Open<\/strong>.
                        \n                        \"PuTTY<\/a><\/li>\n
                      6. Click Open<\/strong>. If this is your first time connecting to this server from PuTTY, a PuTTY Security Alert<\/strong> window may appear. If it does, click Yes<\/strong>.<\/li>\n
                      7. If everything worked correctly, you’ll be connected to the remote host without typing in your NetID password.<\/li>\n<\/ol>\n
                        \n    \t\t\t\t<\/div>\r\n    \t\t\t<\/div>\r\n    \t\t<\/div>\r\n    \t\t\n
                        FAQ<\/h2>\n    \t\t
                        \r\n    \t\t\t
                        I received a warning message about connecting to an unknown server. What should I do?<\/h3><\/div>\r\n    \t\t\t
                        \r\n    \t\t\t\t
                        \r\n    \t\t\t\t\t<\/p>\n
                        When connecting to a remote server, you may receive a warning message along the lines of “Continue connecting to an unknown server and add its host key to a cache?” or “authenticity can’t be established”. If this is your first time connecting to this remote server from this computer using a new SSH key pair, you can safely ignore this warning by clicking Accept<\/strong> or OK<\/strong>.<\/p>\n
                        However, if the warning appears for a second time on the same computer while attempting to connect to the same server with the same key pair, it is worth verifying the hostname and key fingerprints.<\/p>\n
                        1. First, make sure you typed the hostname of the server correctly. The warning message will mention the server it’s trying to authenticate with. If the hostname shown is not the hostname of the server you were expecting, I would recommend clicking Cancel<\/strong> and attempting to connect again, making sure the host name<\/strong> is correct.<\/p>\n
                        2. Next, if the warning message appears again with the correct hostname, select and copy the contents of the warning message, paste them into the Description<\/strong> field of a Help Request to the Tech Team<\/a>,\u00a0 Submit your ticket<\/strong>, Cancel<\/strong> the connection to the server, and wait for a reply from the Systems Architecture and Administration team.<\/p>\n    \t\t\t\t<\/div>\r\n    \t\t\t<\/div>\r\n    \t\t<\/div>\r\n    \t\t\n","protected":false},"excerpt":{"rendered":"
                        SSH keys are an alternative method of authentication, using pre-generated key files in place of a password. This method also currently removes the requirement for Duo multifactor authentication. This article outlines how to generate a key pair, where to save them, and which services will accept SSH key pairs as…<\/p>\n","protected":false},"author":156,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"_relevanssi_hide_post":"","_relevanssi_hide_content":"","_relevanssi_pin_for_all":"","_relevanssi_pin_keywords":"","_relevanssi_unpin_keywords":"","_relevanssi_related_keywords":"","_relevanssi_related_include_ids":"","_relevanssi_related_exclude_ids":"","_relevanssi_related_no_append":"","_relevanssi_related_not_related":"","_relevanssi_related_posts":"","_relevanssi_noindex_reason":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"ht-kb-category":[],"ht-kb-tag":[],"class_list":["post-30959","ht_kb","type-ht_kb","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/www.uvm.edu\/it\/kb\/wp-json\/wp\/v2\/ht-kb\/30959","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.uvm.edu\/it\/kb\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/www.uvm.edu\/it\/kb\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/www.uvm.edu\/it\/kb\/wp-json\/wp\/v2\/users\/156"}],"replies":[{"embeddable":true,"href":"https:\/\/www.uvm.edu\/it\/kb\/wp-json\/wp\/v2\/comments?post=30959"}],"version-history":[{"count":31,"href":"https:\/\/www.uvm.edu\/it\/kb\/wp-json\/wp\/v2\/ht-kb\/30959\/revisions"}],"predecessor-version":[{"id":32655,"href":"https:\/\/www.uvm.edu\/it\/kb\/wp-json\/wp\/v2\/ht-kb\/30959\/revisions\/32655"}],"wp:attachment":[{"href":"https:\/\/www.uvm.edu\/it\/kb\/wp-json\/wp\/v2\/media?parent=30959"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/www.uvm.edu\/it\/kb\/wp-json\/wp\/v2\/ht-kb-category?post=30959"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/www.uvm.edu\/it\/kb\/wp-json\/wp\/v2\/ht-kb-tag?post=30959"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}