title: In what ways is an SSH Key different from tokens for git authentication?
body: <p>I recently started getting notifications about the GitHub deprecation of basic authentication using a password to Git - see their blog post <a href="https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/" rel="noreferrer">https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/</a>.</p>
  <p>In this post, they say the following:</p>
  <blockquote>
  <p>For developers, if you are using a password to authenticate Git operations with GitHub.com today, you must begin using a personal access token over HTTPS (recommended) or SSH key by August 13, 2021, to avoid disruption.</p>
  </blockquote>
  <p>A short while ago, I started using SSH keys on some of the machines I use anyway to avoid entering my password regularly or storing it unencrypted with credential helper. However, as per above, they say personal access tokens are &quot;recommended&quot;.</p>
  <p>What I would like to know is what are the key differences between each of these methods? This is to get some insight into why tokens are &quot;recommended&quot; and whether it is worth switching to this method of authentication.</p>