Merge branch 'main' into 2fa-clarification
This commit is contained in:
Steve Guntrip
@@ -4,13 +4,13 @@ intro: 'You can access {% if currentVersion == "github-ae@latest" %}{% data vari
|
||||
product: '{% data reusables.gated-features.saml-sso %}'
|
||||
redirect_from:
|
||||
- /articles/about-authentication-with-saml-single-sign-on
|
||||
- /github/authenticating-to-github/about-authentication-with-saml-single-sign-on
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- SSO
|
||||
---
|
||||
|
||||
### About authentication with SAML SSO
|
||||
|
||||
{% if currentVersion == "github-ae@latest" %}
|
||||
@@ -4,12 +4,12 @@ intro: 'To use a personal access token with an organization that uses SAML singl
|
||||
redirect_from:
|
||||
- /articles/authorizing-a-personal-access-token-for-use-with-a-saml-single-sign-on-organization/
|
||||
- /articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
|
||||
- /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- SSO
|
||||
---
|
||||
|
||||
You can authorize an existing personal access token, or [create a new personal access token](/github/authenticating-to-github/creating-a-personal-access-token) and then authorize it.
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
@@ -4,12 +4,12 @@ intro: 'To use an SSH key with an organization that uses SAML single sign-on (SS
|
||||
redirect_from:
|
||||
- /articles/authorizing-an-ssh-key-for-use-with-a-saml-single-sign-on-organization/
|
||||
- /articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on
|
||||
- /github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- SSO
|
||||
---
|
||||
|
||||
You can authorize an existing SSH key, or create a new SSH key and then authorize it. For more information about creating a new SSH key, see "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)."
|
||||
|
||||
{% note %}
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Authenticating with SAML single sign-on
|
||||
intro: 'You can authenticate to {% if currentVersion == "free-pro-team@latest" %}a {% data variables.product.product_name %} organization {% elsif currentVersion == "github-ae@latest" %}{% data variables.product.product_location %} {% endif %}with SAML single sign-on (SSO){% if currentVersion == "free-pro-team@latest" %} and view your active sessions{% endif %}.'
|
||||
mapTopic: true
|
||||
product: '{% data reusables.gated-features.saml-sso %}'
|
||||
redirect_from:
|
||||
- /articles/authenticating-to-a-github-organization-with-saml-single-sign-on/
|
||||
@@ -11,5 +10,10 @@ versions:
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- SSO
|
||||
children:
|
||||
- /about-authentication-with-saml-single-sign-on
|
||||
- /authorizing-an-ssh-key-for-use-with-saml-single-sign-on
|
||||
- /authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
|
||||
- /viewing-and-managing-your-active-saml-sessions
|
||||
---
|
||||
|
||||
@@ -3,12 +3,12 @@ title: Viewing and managing your active SAML sessions
|
||||
intro: You can view and revoke your active SAML sessions in your security settings.
|
||||
redirect_from:
|
||||
- /articles/viewing-and-managing-your-active-saml-sessions
|
||||
- /github/authenticating-to-github/viewing-and-managing-your-active-saml-sessions
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- SSO
|
||||
---
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.security %}
|
||||
3. Under "Sessions," you can see your active SAML sessions.
|
||||
@@ -3,6 +3,7 @@ title: About SSH
|
||||
intro: 'Using the SSH protocol, you can connect and authenticate to remote servers and services. With SSH keys, you can connect to {% data variables.product.product_name %} without supplying your username and personal access token at each visit.'
|
||||
redirect_from:
|
||||
- /articles/about-ssh
|
||||
- /github/authenticating-to-github/about-ssh
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -10,7 +11,6 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
When you set up SSH, you will need to generate a new SSH key and add it to the ssh-agent. You must add the SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)."
|
||||
|
||||
You can further secure your SSH key by using a hardware security key, which requires the physical hardware security key to be attached to your computer when the key pair is used to authenticate with SSH. You can also secure your SSH key by adding your key to the ssh-agent and using a passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)."
|
||||
@@ -3,6 +3,7 @@ title: Adding a new SSH key to your GitHub account
|
||||
intro: 'To configure your {% data variables.product.product_name %} account to use your new (or existing) SSH key, you''ll also need to add it to your {% data variables.product.product_name %} account.'
|
||||
redirect_from:
|
||||
- /articles/adding-a-new-ssh-key-to-your-github-account
|
||||
- /github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -10,7 +11,6 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
Before adding a new SSH key to your {% data variables.product.product_name %} account, you should have:
|
||||
* [Checked for existing SSH keys](/articles/checking-for-existing-ssh-keys)
|
||||
* [Generated a new SSH key and added it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)
|
||||
@@ -3,6 +3,7 @@ title: Checking for existing SSH keys
|
||||
intro: 'Before you generate an SSH key, you can check to see if you have any existing SSH keys.'
|
||||
redirect_from:
|
||||
- /articles/checking-for-existing-ssh-keys
|
||||
- /github/authenticating-to-github/checking-for-existing-ssh-keys
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -10,7 +11,6 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
{% data reusables.ssh.dsa-support %}
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
@@ -5,6 +5,7 @@ redirect_from:
|
||||
- /articles/adding-a-new-ssh-key-to-the-ssh-agent/
|
||||
- /articles/generating-a-new-ssh-key/
|
||||
- /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent
|
||||
- /github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -12,7 +13,6 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
### About SSH key generation
|
||||
|
||||
If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)."
|
||||
@@ -10,12 +10,18 @@ redirect_from:
|
||||
- /articles/generating-ssh-keys/
|
||||
- /articles/generating-an-ssh-key/
|
||||
- /articles/connecting-to-github-with-ssh
|
||||
mapTopic: true
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- SSH
|
||||
children:
|
||||
- /about-ssh
|
||||
- /checking-for-existing-ssh-keys
|
||||
- /generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent
|
||||
- /adding-a-new-ssh-key-to-your-github-account
|
||||
- /testing-your-ssh-connection
|
||||
- /working-with-ssh-key-passphrases
|
||||
---
|
||||
|
||||
@@ -3,6 +3,7 @@ title: Testing your SSH connection
|
||||
intro: 'After you''ve set up your SSH key and added it to your {% data variables.product.product_name %} account, you can test your connection.'
|
||||
redirect_from:
|
||||
- /articles/testing-your-ssh-connection
|
||||
- /github/authenticating-to-github/testing-your-ssh-connection
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -10,7 +11,6 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
Before testing your SSH connection, you should have:
|
||||
- [Checked for existing SSH keys](/articles/checking-for-existing-ssh-keys)
|
||||
- [Generated a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)
|
||||
@@ -5,6 +5,7 @@ redirect_from:
|
||||
- /ssh-key-passphrases/
|
||||
- /working-with-key-passphrases/
|
||||
- /articles/working-with-ssh-key-passphrases
|
||||
- /github/authenticating-to-github/working-with-ssh-key-passphrases
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -12,7 +13,6 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
With SSH keys, if someone gains access to your computer, they also gain access to every system that uses that key. To add an extra layer of security, you can add a passphrase to your SSH key. You can use `ssh-agent` to securely save your passphrase so you don't have to reenter it.
|
||||
|
||||
### Adding or changing a passphrase
|
||||
@@ -23,75 +23,13 @@ topics:
|
||||
- Access management
|
||||
- Usernames
|
||||
- Device verification
|
||||
children:
|
||||
- /keeping-your-account-and-data-secure
|
||||
- /securing-your-account-with-two-factor-authentication-2fa
|
||||
- /authenticating-with-saml-single-sign-on
|
||||
- /connecting-to-github-with-ssh
|
||||
- /troubleshooting-ssh
|
||||
- /managing-commit-signature-verification
|
||||
- /troubleshooting-commit-signature-verification
|
||||
---
|
||||
|
||||
|
||||
### Table of Contents
|
||||
|
||||
{% topic_link_in_list /keeping-your-account-and-data-secure %}
|
||||
{% link_in_list /about-authentication-to-github %}
|
||||
{% link_in_list /creating-a-strong-password %}
|
||||
{% link_in_list /updating-your-github-access-credentials %}
|
||||
{% link_in_list /creating-a-personal-access-token %}
|
||||
{% link_in_list /reviewing-your-ssh-keys %}
|
||||
{% link_in_list /reviewing-your-deploy-keys %}
|
||||
{% link_in_list /authorizing-oauth-apps %}
|
||||
{% link_in_list /reviewing-your-authorized-integrations %}
|
||||
{% link_in_list /connecting-with-third-party-applications %}
|
||||
{% link_in_list /reviewing-your-authorized-applications-oauth %}
|
||||
{% link_in_list /reviewing-your-security-log %}
|
||||
{% link_in_list /removing-sensitive-data-from-a-repository %}
|
||||
{% link_in_list /about-anonymized-urls %}
|
||||
{% link_in_list /about-githubs-ip-addresses %}
|
||||
{% link_in_list /githubs-ssh-key-fingerprints %}
|
||||
{% link_in_list /sudo-mode %}
|
||||
{% link_in_list /preventing-unauthorized-access %}
|
||||
{% topic_link_in_list /securing-your-account-with-two-factor-authentication-2fa %}
|
||||
{% link_in_list /about-two-factor-authentication %}
|
||||
{% link_in_list /configuring-two-factor-authentication %}
|
||||
{% link_in_list /configuring-two-factor-authentication-recovery-methods %}
|
||||
{% link_in_list /accessing-github-using-two-factor-authentication %}
|
||||
{% link_in_list /recovering-your-account-if-you-lose-your-2fa-credentials %}
|
||||
{% link_in_list /changing-two-factor-authentication-delivery-methods-for-your-mobile-device %}
|
||||
{% link_in_list /countries-where-sms-authentication-is-supported %}
|
||||
{% link_in_list /disabling-two-factor-authentication-for-your-personal-account %}
|
||||
{% topic_link_in_list /authenticating-with-saml-single-sign-on %}
|
||||
{% link_in_list /about-authentication-with-saml-single-sign-on %}
|
||||
{% link_in_list /authorizing-an-ssh-key-for-use-with-saml-single-sign-on %}
|
||||
{% link_in_list /authorizing-a-personal-access-token-for-use-with-saml-single-sign-on %}
|
||||
{% link_in_list /viewing-and-managing-your-active-saml-sessions %}
|
||||
{% topic_link_in_list /connecting-to-github-with-ssh %}
|
||||
{% link_in_list /about-ssh %}
|
||||
{% link_in_list /checking-for-existing-ssh-keys %}
|
||||
{% link_in_list /generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent %}
|
||||
{% link_in_list /adding-a-new-ssh-key-to-your-github-account %}
|
||||
{% link_in_list /testing-your-ssh-connection %}
|
||||
{% link_in_list /working-with-ssh-key-passphrases %}
|
||||
{% topic_link_in_list /troubleshooting-ssh %}
|
||||
{% link_in_list /using-ssh-over-the-https-port %}
|
||||
{% link_in_list /recovering-your-ssh-key-passphrase %}
|
||||
{% link_in_list /deleted-or-missing-ssh-keys %}
|
||||
{% link_in_list /error-permission-denied-publickey %}
|
||||
{% link_in_list /error-bad-file-number %}
|
||||
{% link_in_list /error-key-already-in-use %}
|
||||
{% link_in_list /error-permission-to-userrepo-denied-to-other-user %}
|
||||
{% link_in_list /error-permission-to-userrepo-denied-to-userother-repo %}
|
||||
{% link_in_list /error-agent-admitted-failure-to-sign %}
|
||||
{% link_in_list /error-ssh-add-illegal-option----k %}
|
||||
{% link_in_list /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok %}
|
||||
{% link_in_list /error-unknown-key-type %}
|
||||
{% link_in_list /error-were-doing-an-ssh-key-audit %}
|
||||
{% topic_link_in_list /managing-commit-signature-verification %}
|
||||
{% link_in_list /about-commit-signature-verification %}
|
||||
{% link_in_list /displaying-verification-statuses-for-all-of-your-commits %}
|
||||
{% link_in_list /checking-for-existing-gpg-keys %}
|
||||
{% link_in_list /generating-a-new-gpg-key %}
|
||||
{% link_in_list /adding-a-new-gpg-key-to-your-github-account %}
|
||||
{% link_in_list /telling-git-about-your-signing-key %}
|
||||
{% link_in_list /associating-an-email-with-your-gpg-key %}
|
||||
{% link_in_list /signing-commits %}
|
||||
{% link_in_list /signing-tags %}
|
||||
{% topic_link_in_list /troubleshooting-commit-signature-verification %}
|
||||
{% link_in_list /checking-your-commit-and-tag-signature-verification-status %}
|
||||
{% link_in_list /updating-an-expired-gpg-key %}
|
||||
{% link_in_list /using-a-verified-email-address-in-your-gpg-key %}
|
||||
|
||||
@@ -1,15 +0,0 @@
|
||||
---
|
||||
title: Keeping your account and data secure
|
||||
intro: 'To protect your personal information, you should keep both your {% data variables.product.product_name %} account and any associated data secure.'
|
||||
mapTopic: true
|
||||
redirect_from:
|
||||
- /articles/keeping-your-account-and-data-secure
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
@@ -5,13 +5,13 @@ redirect_from:
|
||||
- /articles/why-do-my-images-have-strange-urls/
|
||||
- /articles/about-anonymized-image-urls
|
||||
- /authenticating-to-github/about-anonymized-image-urls
|
||||
- /github/authenticating-to-github/about-anonymized-urls
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
To host your images, {% data variables.product.product_name %} uses the [open-source project Camo](https://github.com/atmos/camo). Camo generates an anonymous URL proxy for each file which hides your browser details and related information from other users. The URL starts `https://<subdomain>.githubusercontent.com/`, with different subdomains depending on how you uploaded the image.
|
||||
|
||||
Videos also get anonymized URLs with the same format as image URLs, but are not processed through Camo. This is because {% data variables.product.prodname_dotcom %} does not support externally hosted videos, so the anonymized URL is a link to the uploaded video hosted by {% data variables.product.prodname_dotcom %}.
|
||||
@@ -8,8 +8,9 @@ versions:
|
||||
topics:
|
||||
- Identity
|
||||
- Access management
|
||||
redirect_from:
|
||||
- /github/authenticating-to-github/about-authentication-to-github
|
||||
---
|
||||
|
||||
### About authentication to {% data variables.product.prodname_dotcom %}
|
||||
|
||||
To keep your account secure, you must authenticate before you can access{% if currentVersion != "github-ae@latest" %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be.
|
||||
@@ -8,6 +8,7 @@ redirect_from:
|
||||
- /articles/github-s-ip-addresses/
|
||||
- /articles/about-github-s-ip-addresses
|
||||
- /articles/about-githubs-ip-addresses
|
||||
- /github/authenticating-to-github/about-githubs-ip-addresses
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
@@ -3,6 +3,7 @@ title: Authorizing OAuth Apps
|
||||
intro: 'You can connect your {% data variables.product.product_name %} identity to third-party applications using OAuth. When authorizing an {% data variables.product.prodname_oauth_app %}, you should ensure you trust the application, review who it''s developed by, and review the kinds of information the application wants to access.'
|
||||
redirect_from:
|
||||
- /articles/authorizing-oauth-apps
|
||||
- /github/authenticating-to-github/authorizing-oauth-apps
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -11,7 +12,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
When an {% data variables.product.prodname_oauth_app %} wants to identify you by your {% data variables.product.product_name %} account, you'll see a page with the app's developer contact information and a list of the specific data that's being requested.
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
@@ -3,6 +3,7 @@ title: Connecting with third-party applications
|
||||
intro: 'You can connect your {% data variables.product.product_name %} identity to third-party applications using OAuth. When authorizing one of these applications, you should ensure you trust the application, review who it''s developed by, and review the kinds of information the application wants to access.'
|
||||
redirect_from:
|
||||
- /articles/connecting-with-third-party-applications
|
||||
- /github/authenticating-to-github/connecting-with-third-party-applications
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -11,7 +12,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
When a third-party application wants to identify you by your {% data variables.product.product_name %} login, you'll see a page with the developer contact information and a list of the specific data that's being requested.
|
||||
|
||||
### Contacting the application developer
|
||||
@@ -6,6 +6,7 @@ redirect_from:
|
||||
- /articles/creating-an-access-token-for-command-line-use/
|
||||
- /articles/creating-a-personal-access-token-for-the-command-line
|
||||
- /github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line
|
||||
- /github/authenticating-to-github/creating-a-personal-access-token
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -14,7 +15,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
Personal access tokens (PATs) are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line).
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %}
|
||||
@@ -4,6 +4,7 @@ intro: 'Secure your {% data variables.product.product_name %} account with a str
|
||||
redirect_from:
|
||||
- /articles/what-is-a-strong-password/
|
||||
- /articles/creating-a-strong-password
|
||||
- /github/authenticating-to-github/creating-a-strong-password
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -11,7 +12,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
You must choose or generate a password for your {% data variables.product.product_name %} account that is at least:
|
||||
- {% if enterpriseServerVersions contains currentVersion %}Seven{% else %}Eight{% endif %} characters long, if it includes a number and a lowercase letter, or
|
||||
- 15 characters long with any combination of characters
|
||||
@@ -5,13 +5,13 @@ redirect_from:
|
||||
- /articles/what-are-github-s-ssh-key-fingerprints/
|
||||
- /articles/github-s-ssh-key-fingerprints
|
||||
- /articles/githubs-ssh-key-fingerprints
|
||||
- /github/authenticating-to-github/githubs-ssh-key-fingerprints
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
|
||||
|
||||
- `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA)
|
||||
@@ -0,0 +1,32 @@
|
||||
---
|
||||
title: Keeping your account and data secure
|
||||
intro: 'To protect your personal information, you should keep both your {% data variables.product.product_name %} account and any associated data secure.'
|
||||
redirect_from:
|
||||
- /articles/keeping-your-account-and-data-secure
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- Identity
|
||||
- Access management
|
||||
children:
|
||||
- /about-authentication-to-github
|
||||
- /creating-a-strong-password
|
||||
- /updating-your-github-access-credentials
|
||||
- /creating-a-personal-access-token
|
||||
- /reviewing-your-ssh-keys
|
||||
- /reviewing-your-deploy-keys
|
||||
- /authorizing-oauth-apps
|
||||
- /reviewing-your-authorized-integrations
|
||||
- /connecting-with-third-party-applications
|
||||
- /reviewing-your-authorized-applications-oauth
|
||||
- /reviewing-your-security-log
|
||||
- /removing-sensitive-data-from-a-repository
|
||||
- /about-anonymized-urls
|
||||
- /about-githubs-ip-addresses
|
||||
- /githubs-ssh-key-fingerprints
|
||||
- /sudo-mode
|
||||
- /preventing-unauthorized-access
|
||||
---
|
||||
|
||||
@@ -3,6 +3,7 @@ title: Preventing unauthorized access
|
||||
intro: 'You may be alerted to a security incident in the media, such as the discovery of the [Heartbleed bug](http://heartbleed.com/), or your computer could be stolen while you''re signed in to {% data variables.product.product_location %}. In such cases, changing your password prevents any unintended future access to your account and projects.'
|
||||
redirect_from:
|
||||
- /articles/preventing-unauthorized-access
|
||||
- /github/authenticating-to-github/preventing-unauthorized-access
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -10,7 +11,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
{% data variables.product.product_name %} requires a password to perform sensitive actions, such as adding new SSH keys, authorizing applications, or modifying team members.
|
||||
|
||||
After changing your password, you should perform these actions to make sure that your account is secure:
|
||||
@@ -6,6 +6,7 @@ redirect_from:
|
||||
- /removing-sensitive-data/
|
||||
- /articles/remove-sensitive-data/
|
||||
- /articles/removing-sensitive-data-from-a-repository
|
||||
- /github/authenticating-to-github/removing-sensitive-data-from-a-repository
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -14,7 +15,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
The `git filter-branch` command and the BFG Repo-Cleaner rewrite your repository's history, which changes the SHAs for existing commits that you alter and any dependent commits. Changed commit SHAs may affect open pull requests in your repository. We recommend merging or closing all open pull requests before removing files from your repository.
|
||||
|
||||
You can remove the file from the latest commit with `git rm`. For information on removing a file that was added with the latest commit, see "[Removing files from a repository's history](/articles/removing-files-from-a-repository-s-history)."
|
||||
@@ -3,6 +3,7 @@ title: Reviewing your authorized applications (OAuth)
|
||||
intro: 'You should review your authorized applications to verify that no new applications with expansive permissions are authorized, such as those that have access to your private repositories.'
|
||||
redirect_from:
|
||||
- /articles/reviewing-your-authorized-applications-oauth
|
||||
- /github/authenticating-to-github/reviewing-your-authorized-applications-oauth
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -11,7 +12,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.access_applications %}
|
||||
{% data reusables.user_settings.access_authorized_oauth_apps %}
|
||||
@@ -3,6 +3,7 @@ title: Reviewing your authorized integrations
|
||||
intro: You can review your authorized integrations to audit the access that each integration has to your account and data.
|
||||
redirect_from:
|
||||
- /articles/reviewing-your-authorized-integrations
|
||||
- /github/authenticating-to-github/reviewing-your-authorized-integrations
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -11,7 +12,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
### Reviewing your authorized {% data variables.product.prodname_oauth_app %}s
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
@@ -3,6 +3,7 @@ title: Reviewing your deploy keys
|
||||
intro: You should review deploy keys to ensure that there aren't any unauthorized (or possibly compromised) keys. You can also approve existing deploy keys that are valid.
|
||||
redirect_from:
|
||||
- /articles/reviewing-your-deploy-keys
|
||||
- /github/authenticating-to-github/reviewing-your-deploy-keys
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -11,7 +12,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
3. In the left sidebar, click **Deploy keys**.
|
||||
@@ -4,6 +4,7 @@ intro: You can review the security log for your user account to better understan
|
||||
miniTocMaxHeadingLevel: 4
|
||||
redirect_from:
|
||||
- /articles/reviewing-your-security-log
|
||||
- /github/authenticating-to-github/reviewing-your-security-log
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -12,7 +13,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
### Accessing your security log
|
||||
|
||||
The security log lists all actions performed within the last 90 days{% if currentVersion ver_lt "enterprise-server@2.20" %}, up to 50{% endif %}.
|
||||
@@ -5,6 +5,7 @@ redirect_from:
|
||||
- /articles/keeping-your-application-access-tokens-safe/
|
||||
- /articles/keeping-your-ssh-keys-and-application-access-tokens-safe/
|
||||
- /articles/reviewing-your-ssh-keys
|
||||
- /github/authenticating-to-github/reviewing-your-ssh-keys
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -13,7 +14,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
You can delete unauthorized (or possibly compromised) SSH keys to ensure that an attacker no longer has access to your repositories. You can also approve existing SSH keys that are valid.
|
||||
|
||||
{% mac %}
|
||||
@@ -3,6 +3,7 @@ title: Sudo mode
|
||||
intro: '{% data variables.product.product_name %} asks you for your password before you can modify your email address, authorize third-party applications, or add new public keys, or initiate other *sudo-protected* actions.'
|
||||
redirect_from:
|
||||
- /articles/sudo-mode
|
||||
- /github/authenticating-to-github/sudo-mode
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -10,7 +11,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
After you've performed a sudo-protected action, you'll only be asked to re-authenticate again after a few hours of inactivity. Every sudo-protected action resets this timer.
|
||||
|
||||
|
||||
@@ -5,6 +5,7 @@ redirect_from:
|
||||
- /articles/rolling-your-credentials/
|
||||
- /articles/how-can-i-reset-my-password/
|
||||
- /articles/updating-your-github-access-credentials
|
||||
- /github/authenticating-to-github/updating-your-github-access-credentials
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -13,7 +14,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
{% if currentVersion != "github-ae@latest" %}
|
||||
### Requesting a new password
|
||||
|
||||
@@ -5,6 +5,7 @@ redirect_from:
|
||||
- /articles/about-gpg-commit-and-tag-signatures/
|
||||
- /articles/about-gpg/
|
||||
- /articles/about-commit-signature-verification
|
||||
- /github/authenticating-to-github/about-commit-signature-verification
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -13,7 +14,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
### About commit signature verification
|
||||
|
||||
You can sign commits and tags locally, to give other people confidence about the origin of a change you have made. If a commit or tag has a GPG or S/MIME signature that is cryptographically verifiable, GitHub marks the commit or tag {% if currentVersion == "free-pro-team@latest" %}"Verified" or "Partially verified."{% else %}"Verified."{% endif %}
|
||||
@@ -3,6 +3,7 @@ title: Adding a new GPG key to your GitHub account
|
||||
intro: 'To configure your {% data variables.product.product_name %} account to use your new (or existing) GPG key, you''ll also need to add it to your {% data variables.product.product_name %} account.'
|
||||
redirect_from:
|
||||
- /articles/adding-a-new-gpg-key-to-your-github-account
|
||||
- /github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -11,7 +12,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
Before adding a new GPG key to your {% data variables.product.product_name %} account, you should have:
|
||||
- [Checked for existing GPG keys](/articles/checking-for-existing-gpg-keys)
|
||||
- [Generated and copied a new GPG key](/articles/generating-a-new-gpg-key)
|
||||
@@ -3,6 +3,7 @@ title: Associating an email with your GPG key
|
||||
intro: 'Your GPG key must be associated with a {% data variables.product.product_name %} verified email that matches your committer identity.'
|
||||
redirect_from:
|
||||
- /articles/associating-an-email-with-your-gpg-key
|
||||
- /github/authenticating-to-github/associating-an-email-with-your-gpg-key
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -3,6 +3,7 @@ title: Checking for existing GPG keys
|
||||
intro: 'Before you generate a GPG key, you can check to see if you have any existing GPG keys.'
|
||||
redirect_from:
|
||||
- /articles/checking-for-existing-gpg-keys
|
||||
- /github/authenticating-to-github/checking-for-existing-gpg-keys
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -7,8 +7,9 @@ versions:
|
||||
topics:
|
||||
- Identity
|
||||
- Access management
|
||||
redirect_from:
|
||||
- /github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits
|
||||
---
|
||||
|
||||
{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
|
||||
|
||||
### About vigilant mode
|
||||
@@ -3,6 +3,7 @@ title: Generating a new GPG key
|
||||
intro: 'If you don''t have an existing GPG key, you can generate a new GPG key to use for signing commits and tags.'
|
||||
redirect_from:
|
||||
- /articles/generating-a-new-gpg-key
|
||||
- /github/authenticating-to-github/generating-a-new-gpg-key
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -11,7 +12,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
{% data reusables.gpg.supported-gpg-key-algorithms %}
|
||||
|
||||
### Generating a GPG key
|
||||
@@ -5,7 +5,6 @@ redirect_from:
|
||||
- /articles/generating-a-gpg-key/
|
||||
- /articles/signing-commits-with-gpg/
|
||||
- /articles/managing-commit-signature-verification
|
||||
mapTopic: true
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -13,5 +12,15 @@ versions:
|
||||
topics:
|
||||
- Identity
|
||||
- Access management
|
||||
children:
|
||||
- /about-commit-signature-verification
|
||||
- /displaying-verification-statuses-for-all-of-your-commits
|
||||
- /checking-for-existing-gpg-keys
|
||||
- /generating-a-new-gpg-key
|
||||
- /adding-a-new-gpg-key-to-your-github-account
|
||||
- /telling-git-about-your-signing-key
|
||||
- /associating-an-email-with-your-gpg-key
|
||||
- /signing-commits
|
||||
- /signing-tags
|
||||
---
|
||||
|
||||
@@ -5,6 +5,7 @@ redirect_from:
|
||||
- /articles/signing-commits-and-tags-using-gpg/
|
||||
- /articles/signing-commits-using-gpg/
|
||||
- /articles/signing-commits
|
||||
- /github/authenticating-to-github/signing-commits
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -4,6 +4,7 @@ intro: You can sign tags locally using GPG or S/MIME.
|
||||
redirect_from:
|
||||
- /articles/signing-tags-using-gpg/
|
||||
- /articles/signing-tags
|
||||
- /github/authenticating-to-github/signing-tags
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -12,7 +13,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
{% data reusables.gpg.desktop-support-for-commit-signing %}
|
||||
|
||||
1. To sign a tag, add `-s` to your `git tag` command.
|
||||
@@ -4,6 +4,7 @@ intro: 'To sign commits locally, you need to inform Git that there''s a GPG or X
|
||||
redirect_from:
|
||||
- /articles/telling-git-about-your-gpg-key/
|
||||
- /articles/telling-git-about-your-signing-key
|
||||
- /github/authenticating-to-github/telling-git-about-your-signing-key
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -12,7 +13,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
{% mac %}
|
||||
|
||||
### Telling Git about your GPG key
|
||||
@@ -3,13 +3,13 @@ title: About two-factor authentication
|
||||
intro: '{% data reusables.two_fa.about-2fa %} With 2FA, you have to log in with your username and password and provide another form of authentication that only you know or have access to.'
|
||||
redirect_from:
|
||||
- /articles/about-two-factor-authentication
|
||||
- /github/authenticating-to-github/about-two-factor-authentication
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
For {% data variables.product.product_name %}, the second form of authentication is a code that's generated by an application on your mobile device{% if currentVersion == "free-pro-team@latest" %} or sent as a text message (SMS){% endif %}. After you enable 2FA, {% data variables.product.product_name %} generates an authentication code any time someone attempts to sign into your {% data variables.product.product_name %} account. The only way someone can sign into your account is if they know both your password and have access to the authentication code on your phone.
|
||||
|
||||
{% data reusables.two_fa.after-2fa-add-security-key %}
|
||||
@@ -6,13 +6,13 @@ redirect_from:
|
||||
- /articles/providing-your-2fa-authentication-code/
|
||||
- /articles/authenticating-to-github-using-fido-u2f-via-nfc/
|
||||
- /articles/accessing-github-using-two-factor-authentication
|
||||
- /github/authenticating-to-github/accessing-github-using-two-factor-authentication
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
With two-factor authentication enabled, you'll need to provide an authentication code when accessing {% data variables.product.product_name %} through your browser. If you access {% data variables.product.product_name %} using other methods, such as the API or the command line, you'll need to use an alternative form of authentication. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)."
|
||||
|
||||
### Providing a 2FA code when signing in to the website
|
||||
@@ -4,12 +4,12 @@ intro: You can switch between receiving authentication codes through a text mess
|
||||
redirect_from:
|
||||
- /articles/changing-two-factor-authentication-delivery-methods/
|
||||
- /articles/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
|
||||
- /github/authenticating-to-github/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Changing your two-factor authentication method invalidates your current two-factor method setup. However, this doesn't affect your recovery codes or fallback SMS configuration. You can update your recovery codes or fallback SMS configuration on in your personal account's security settings page if desired.
|
||||
@@ -8,13 +8,13 @@ redirect_from:
|
||||
- /articles/adding-a-fallback-authentication-method-with-recover-accounts-elsewhere/
|
||||
- /articles/generating-and-storing-an-account-recovery-token/
|
||||
- /articles/configuring-two-factor-authentication-recovery-methods
|
||||
- /github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
In addition to securely storing your two-factor authentication recovery codes, we strongly recommend configuring one or more additional recovery methods.
|
||||
|
||||
### Downloading your two-factor authentication recovery codes
|
||||
@@ -6,13 +6,13 @@ redirect_from:
|
||||
- /articles/configuring-two-factor-authentication-via-text-message/
|
||||
- /articles/configuring-two-factor-authentication-via-fido-u2f/
|
||||
- /articles/configuring-two-factor-authentication
|
||||
- /github/authenticating-to-github/configuring-two-factor-authentication
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
You can configure two-factor authentication using a mobile app{% if currentVersion == "free-pro-team@latest" %} or via text message{% endif %}. You can also add a security key.
|
||||
|
||||
We strongly recommend using a time-based one-time password (TOTP) application to configure 2FA.{% if currentVersion == "free-pro-team@latest" %} TOTP applications are more reliable than SMS, especially for locations outside the United States.{% endif %} TOTP apps support the secure backup of your authentication codes in the cloud and can be restored if you lose access to your device.
|
||||
@@ -31,6 +31,7 @@ A time-based one-time password (TOTP) application automatically generates an aut
|
||||
- [1Password](https://support.1password.com/one-time-passwords/)
|
||||
- [Authy](https://authy.com/guides/github/)
|
||||
- [LastPass Authenticator](https://lastpass.com/auth/)
|
||||
- [Microsoft Authenticator](https://www.microsoft.com/en-us/account/authenticator/)
|
||||
|
||||
{% tip %}
|
||||
|
||||
@@ -3,12 +3,12 @@ title: Countries where SMS authentication is supported
|
||||
intro: 'Because of delivery success rates, {% data variables.product.product_name %} only supports two-factor authentication via SMS for certain countries.'
|
||||
redirect_from:
|
||||
- /articles/countries-where-sms-authentication-is-supported
|
||||
- /github/authenticating-to-github/countries-where-sms-authentication-is-supported
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
If we don't support two-factor authentication via text message for your country of residence, you can set up authentication via a TOTP mobile application. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
|
||||
|
||||
### Supported countries for SMS authentication
|
||||
@@ -3,13 +3,13 @@ title: Disabling two-factor authentication for your personal account
|
||||
intro: 'If you disable two-factor authentication for your personal account, you may lose access to organizations you belong to.'
|
||||
redirect_from:
|
||||
- /articles/disabling-two-factor-authentication-for-your-personal-account
|
||||
- /github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
We strongly recommend using two-factor authentication to secure your account. If you need to disable 2FA, we recommend re-enabling it as soon as possible.
|
||||
|
||||
{% warning %}
|
||||
@@ -5,11 +5,19 @@ redirect_from:
|
||||
- /categories/84/articles/
|
||||
- /categories/two-factor-authentication-2fa/
|
||||
- /articles/securing-your-account-with-two-factor-authentication-2fa
|
||||
mapTopic: true
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
children:
|
||||
- /about-two-factor-authentication
|
||||
- /configuring-two-factor-authentication
|
||||
- /configuring-two-factor-authentication-recovery-methods
|
||||
- /accessing-github-using-two-factor-authentication
|
||||
- /recovering-your-account-if-you-lose-your-2fa-credentials
|
||||
- /changing-two-factor-authentication-delivery-methods-for-your-mobile-device
|
||||
- /countries-where-sms-authentication-is-supported
|
||||
- /disabling-two-factor-authentication-for-your-personal-account
|
||||
---
|
||||
|
||||
@@ -5,13 +5,13 @@ redirect_from:
|
||||
- /articles/recovering-your-account-if-you-lost-your-2fa-credentials/
|
||||
- /articles/authenticating-with-an-account-recovery-token/
|
||||
- /articles/recovering-your-account-if-you-lose-your-2fa-credentials
|
||||
- /github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
{% warning %}
|
||||
@@ -4,6 +4,7 @@ intro: 'You can check the verification status of your commit and tag signatures
|
||||
redirect_from:
|
||||
- /articles/checking-your-gpg-commit-and-tag-signature-verification-status/
|
||||
- /articles/checking-your-commit-and-tag-signature-verification-status
|
||||
- /github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -12,7 +13,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
### Checking your commit signature verification status
|
||||
|
||||
1. On {% data variables.product.product_name %}, navigate to your pull request.
|
||||
@@ -4,7 +4,6 @@ intro: 'You may need to troubleshoot unexpected issues that arise when signing c
|
||||
redirect_from:
|
||||
- /articles/troubleshooting-gpg/
|
||||
- /articles/troubleshooting-commit-signature-verification
|
||||
mapTopic: true
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -12,5 +11,9 @@ versions:
|
||||
topics:
|
||||
- Identity
|
||||
- Access management
|
||||
children:
|
||||
- /checking-your-commit-and-tag-signature-verification-status
|
||||
- /updating-an-expired-gpg-key
|
||||
- /using-a-verified-email-address-in-your-gpg-key
|
||||
---
|
||||
|
||||
@@ -3,6 +3,7 @@ title: Updating an expired GPG key
|
||||
intro: 'When verifying a signature, {% data variables.product.product_name %} checks that the key is not revoked or expired. If your signing key is revoked or expired, {% data variables.product.product_name %} cannot verify your signatures. If your key is revoked, use the primary key or another key that is not revoked to sign your commits.'
|
||||
redirect_from:
|
||||
- /articles/updating-an-expired-gpg-key
|
||||
- /github/authenticating-to-github/updating-an-expired-gpg-key
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -11,7 +12,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
If your key is expired, you must [update the expiration](https://www.gnupg.org/gph/en/manual/c235.html#AEN328), export the new key, delete the expired key in your GitHub account, and [upload the new key to GitHub](/articles/adding-a-new-gpg-key-to-your-github-account/). Your previous commits and tags will show as verified, as long as the key meets all other verification requirements.
|
||||
|
||||
If your key is invalid and you don't use another valid key in your key set, but instead generate a new GPG key with a new set of credentials, then your commits made with the revoked or expired key will continue to show as unverified. Also, your new credentials will not be able to resign or verify your old commits and tags.
|
||||
@@ -3,6 +3,7 @@ title: Using a verified email address in your GPG key
|
||||
intro: 'When verifying a signature, {% data variables.product.product_name %} checks that the committer or tagger email address matches an email address from the GPG key''s identities and is a verified email address on the user''s account. This ensures that the key belongs to you and that you created the commit or tag.'
|
||||
redirect_from:
|
||||
- /articles/using-a-verified-email-address-in-your-gpg-key
|
||||
- /github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -11,7 +12,6 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
If you need to verify your GitHub email address, see "[Verifying your email address](/articles/verifying-your-email-address/)." {% endif %}If you need to update or add an email address to your GPG key, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)."
|
||||
|
||||
@@ -1,14 +0,0 @@
|
||||
---
|
||||
title: Troubleshooting SSH
|
||||
intro: 'When using SSH to connect and authenticate to {% data variables.product.product_name %}, you may need to troubleshoot unexpected issues that may arise.'
|
||||
mapTopic: true
|
||||
redirect_from:
|
||||
- /articles/troubleshooting-ssh
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
@@ -3,12 +3,12 @@ title: Deleted or missing SSH keys
|
||||
intro: 'As a security precaution, {% data variables.product.prodname_dotcom %} automatically deletes SSH keys that haven''t been used in a year.'
|
||||
redirect_from:
|
||||
- /articles/deleted-or-missing-ssh-keys
|
||||
- /github/authenticating-to-github/deleted-or-missing-ssh-keys
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
{% data variables.product.prodname_dotcom %} automatically deletes inactive SSH keys to help keep accounts safe, such as after someone leaves a job or loses a computer.
|
||||
|
||||
You can check if you haven't used an SSH key in a year by reviewing your account's security log. For more information, see "[Reviewing your security log](/articles/reviewing-your-security-log/)."
|
||||
@@ -4,6 +4,7 @@ intro: 'In rare circumstances, connecting to {% data variables.product.product_n
|
||||
redirect_from:
|
||||
- /articles/error-agent-admitted-failure-to-sign-using-the-key/
|
||||
- /articles/error-agent-admitted-failure-to-sign
|
||||
- /github/authenticating-to-github/error-agent-admitted-failure-to-sign
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -11,7 +12,6 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
When trying to SSH into {% data variables.product.product_location %} on a Linux computer, you may see the following message in your terminal:
|
||||
|
||||
```shell
|
||||
@@ -3,6 +3,7 @@ title: 'Error: Bad file number'
|
||||
intro: This error usually means you were unable to connect to the server. Often this is caused by firewalls and proxy servers.
|
||||
redirect_from:
|
||||
- /articles/error-bad-file-number
|
||||
- /github/authenticating-to-github/error-bad-file-number
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -10,7 +11,6 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
When running remote Git commands or SSH, your connection might time out:
|
||||
|
||||
```shell
|
||||
@@ -3,6 +3,7 @@ title: 'Error: Key already in use'
|
||||
intro: 'This error occurs when you try to [add a key](/articles/adding-a-new-ssh-key-to-your-github-account) that''s already been added to another account or repository.'
|
||||
redirect_from:
|
||||
- /articles/error-key-already-in-use
|
||||
- /github/authenticating-to-github/error-key-already-in-use
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -10,7 +11,6 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
### Finding where the key has been used
|
||||
|
||||
To determine where the key has already been used, open a terminal and type the `ssh` command. Use the `-i` flag to provide the path to the key you want to check:
|
||||
@@ -3,6 +3,7 @@ title: 'Error: Permission denied (publickey)'
|
||||
intro: 'A "Permission denied" error means that the server rejected your connection. There could be several reasons why, and the most common examples are explained below.'
|
||||
redirect_from:
|
||||
- /articles/error-permission-denied-publickey
|
||||
- /github/authenticating-to-github/error-permission-denied-publickey
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -10,7 +11,6 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
### Should the `sudo` command be used with Git?
|
||||
|
||||
You should not be using the `sudo` command with Git. If you have a *very good reason* you must use `sudo`, then ensure you are using it with every command (it's probably just better to use `su` to get a shell as root at that point). If you [generate SSH keys](/articles/generating-an-ssh-key) without `sudo` and then try to use a command like `sudo git push`, you won't be using the same keys that you generated.
|
||||
@@ -4,6 +4,7 @@ intro: This error means the key you are pushing with is attached to an account w
|
||||
redirect_from:
|
||||
- /articles/error-permission-to-user-repo-denied-to-other-user
|
||||
- /articles/error-permission-to-userrepo-denied-to-other-user
|
||||
- /github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -11,5 +12,4 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
To fix this, the owner of the repository (`user`) needs to add your account (`other-user`) as a collaborator on the repository or to a team that has write access to the repository.
|
||||
@@ -4,6 +4,7 @@ intro: 'This error means the key you are pushing with is attached to another rep
|
||||
redirect_from:
|
||||
- /articles/error-permission-to-user-repo-denied-to-user-other-repo
|
||||
- /articles/error-permission-to-userrepo-denied-to-userother-repo
|
||||
- /github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -11,7 +12,6 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
To fix this, remove the deploy key from the repository, and [add the key to your user account](/articles/adding-a-new-ssh-key-to-your-github-account) instead.
|
||||
|
||||
If the key you are using is intended to be a deploy key, check out [our guide on deploy keys](/guides/managing-deploy-keys) for more details.
|
||||
@@ -4,6 +4,7 @@ intro: 'This error means your version of `ssh-add` does not support macOS keycha
|
||||
redirect_from:
|
||||
- /articles/error-ssh-add-illegal-option-k
|
||||
- /articles/error-ssh-add-illegal-option----k
|
||||
- /github/authenticating-to-github/error-ssh-add-illegal-option----k
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -11,7 +12,6 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
The `-K` option is in Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an ssh key to the ssh-agent. If you have installed a different version of `ssh-add`, it may lack support for `-K`.
|
||||
|
||||
### Solving the issue
|
||||
@@ -3,6 +3,7 @@ title: 'Error: SSL certificate problem, verify that the CA cert is OK'
|
||||
intro: 'This error means your CA root certificate is out of date. If your CA root certificate needs to be updated, you won''t be able to push or pull from {% data variables.product.product_name %} repositories.'
|
||||
redirect_from:
|
||||
- /articles/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok
|
||||
- /github/authenticating-to-github/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
@@ -4,11 +4,12 @@ intro: 'This error means that the SSH key type you used was unrecognized or is u
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.2'
|
||||
github-ae: 'next'
|
||||
github-ae: next
|
||||
topics:
|
||||
- SSH
|
||||
redirect_from:
|
||||
- /github/authenticating-to-github/error-unknown-key-type
|
||||
---
|
||||
|
||||
### About the `unknown key type` error
|
||||
|
||||
When you generate a new SSH key, you may receive an `unknown key type` error if your SSH client does not support the key type that you specify.{% mac %}To solve this issue on macOS, you can update your SSH client or install a new SSH client.
|
||||
@@ -32,4 +33,4 @@ If you remove OpenSSH, the passphrases that are stored in your keychain will onc
|
||||
3. Quit and relaunch Terminal.
|
||||
4. Try the procedure for generating a new SSH key again. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)."
|
||||
|
||||
{% endmac %}{% linux %}To solve this issue on Linux, use the package manager for your Linux distribution to install a new version of OpenSSH, or compile a new version from source. If you install a different version of OpenSSH, the ability of other applications to authenticate via SSH may be affected. For more information, review the documentation for your distribution.{% endlinux %}
|
||||
{% endmac %}{% linux %}To solve this issue on Linux, use the package manager for your Linux distribution to install a new version of OpenSSH, or compile a new version from source. If you install a different version of OpenSSH, the ability of other applications to authenticate via SSH may be affected. For more information, review the documentation for your distribution.{% endlinux %}
|
||||
@@ -4,6 +4,7 @@ intro: This error means the SSH key you're using to perform a Git operation is u
|
||||
redirect_from:
|
||||
- /articles/error-we-re-doing-an-ssh-key-audit
|
||||
- /articles/error-were-doing-an-ssh-key-audit
|
||||
- /github/authenticating-to-github/error-were-doing-an-ssh-key-audit
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -11,7 +12,6 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
When using an unverified key to perform Git operations, you will be prompted to perform an audit of your SSH keys.
|
||||
|
||||
```shell
|
||||
@@ -0,0 +1,27 @@
|
||||
---
|
||||
title: Troubleshooting SSH
|
||||
intro: 'When using SSH to connect and authenticate to {% data variables.product.product_name %}, you may need to troubleshoot unexpected issues that may arise.'
|
||||
redirect_from:
|
||||
- /articles/troubleshooting-ssh
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- SSH
|
||||
children:
|
||||
- /using-ssh-over-the-https-port
|
||||
- /recovering-your-ssh-key-passphrase
|
||||
- /deleted-or-missing-ssh-keys
|
||||
- /error-permission-denied-publickey
|
||||
- /error-bad-file-number
|
||||
- /error-key-already-in-use
|
||||
- /error-permission-to-userrepo-denied-to-other-user
|
||||
- /error-permission-to-userrepo-denied-to-userother-repo
|
||||
- /error-agent-admitted-failure-to-sign
|
||||
- /error-ssh-add-illegal-option----k
|
||||
- /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok
|
||||
- /error-unknown-key-type
|
||||
- /error-were-doing-an-ssh-key-audit
|
||||
---
|
||||
|
||||
@@ -5,6 +5,7 @@ redirect_from:
|
||||
- /articles/how-do-i-recover-my-passphrase/
|
||||
- /articles/how-do-i-recover-my-ssh-key-passphrase/
|
||||
- /articles/recovering-your-ssh-key-passphrase
|
||||
- /github/authenticating-to-github/recovering-your-ssh-key-passphrase
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -12,7 +13,6 @@ versions:
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
{% mac %}
|
||||
|
||||
If you [configured your SSH passphrase with the macOS keychain](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), you may be able to recover it.
|
||||
@@ -3,12 +3,12 @@ title: Using SSH over the HTTPS port
|
||||
intro: 'Sometimes, firewalls refuse to allow SSH connections entirely. If using [HTTPS cloning with credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git) is not an option, you can attempt to clone using an SSH connection made over the HTTPS port. Most firewall rules should allow this, but proxy servers may interfere.'
|
||||
redirect_from:
|
||||
- /articles/using-ssh-over-the-https-port
|
||||
- /github/authenticating-to-github/using-ssh-over-the-https-port
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- SSH
|
||||
---
|
||||
|
||||
{% tip %}
|
||||
|
||||
**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} via SSH over the HTTPS port is currently not supported.
|
||||
Reference in New Issue
Block a user