add topic frontmatter to articles (#18245)
This commit is contained in:
Rachael Sewell
@@ -6,6 +6,9 @@ redirect_from:
|
||||
- /articles/about-anonymized-image-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 image 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.
|
||||
|
||||
@@ -5,6 +5,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
### About authentication to {% data variables.product.prodname_dotcom %}
|
||||
|
||||
@@ -7,6 +7,8 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- sso
|
||||
---
|
||||
|
||||
### About authentication with SAML SSO
|
||||
|
||||
@@ -9,6 +9,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
### About commit signature verification
|
||||
|
||||
@@ -10,6 +10,9 @@ redirect_from:
|
||||
- /articles/about-githubs-ip-addresses
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP addresses from the [meta](https://api.github.com/meta) API endpoint. For more information, see "[Meta](/rest/reference/meta)."
|
||||
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
When you set up SSH, you'll [generate an SSH key and add it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) and then [add the key to your {% data variables.product.product_name %} account](/articles/adding-a-new-ssh-key-to-your-github-account). Adding the SSH key to the ssh-agent ensures that your SSH key has an extra layer of security through the use of a passphrase. For more information, see "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
|
||||
|
||||
@@ -6,6 +6,8 @@ redirect_from:
|
||||
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.
|
||||
|
||||
@@ -9,6 +9,8 @@ redirect_from:
|
||||
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)."
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
Before adding a new GPG key to your {% data variables.product.product_name %} account, you should have:
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
Before adding a new SSH key to your {% data variables.product.product_name %} account, you should have:
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -9,5 +9,7 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- sso
|
||||
---
|
||||
|
||||
|
||||
@@ -6,6 +6,8 @@ redirect_from:
|
||||
- /articles/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.
|
||||
|
||||
@@ -6,6 +6,8 @@ redirect_from:
|
||||
- /articles/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)."
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
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.
|
||||
|
||||
@@ -6,6 +6,8 @@ redirect_from:
|
||||
- /articles/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
{% data reusables.gpg.supported-gpg-key-algorithms %}
|
||||
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
{% data reusables.ssh.dsa-support %}
|
||||
|
||||
@@ -8,6 +8,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
### Checking your commit signature verification status
|
||||
|
||||
@@ -11,6 +11,8 @@ redirect_from:
|
||||
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.
|
||||
|
||||
@@ -9,6 +9,8 @@ redirect_from:
|
||||
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.
|
||||
|
||||
@@ -15,5 +15,7 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
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.
|
||||
|
||||
@@ -5,6 +5,8 @@ redirect_from:
|
||||
- /articles/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)."
|
||||
|
||||
@@ -10,6 +10,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
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).
|
||||
|
||||
@@ -7,6 +7,9 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
You must choose or generate a password for your {% data variables.product.product_name %} account that is at least:
|
||||
|
||||
@@ -5,6 +5,8 @@ redirect_from:
|
||||
- /articles/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.
|
||||
|
||||
@@ -6,6 +6,8 @@ redirect_from:
|
||||
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.
|
||||
|
||||
@@ -8,6 +8,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
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:
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
When running remote Git commands or SSH, your connection might time out:
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
### Finding where the key has been used
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
### Should the `sudo` command be used with Git?
|
||||
|
||||
@@ -8,6 +8,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
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.
|
||||
|
||||
@@ -8,6 +8,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
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.
|
||||
|
||||
@@ -8,6 +8,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
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`.
|
||||
|
||||
@@ -5,6 +5,8 @@ redirect_from:
|
||||
- /articles/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
The error you receive may look like the following:
|
||||
|
||||
|
||||
@@ -8,6 +8,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
When using an unverified key to perform Git operations, you will be prompted to perform an audit of your SSH keys.
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
{% data reusables.gpg.supported-gpg-key-algorithms %}
|
||||
|
||||
@@ -9,6 +9,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
If you don't already have an SSH key, you must [generate a new SSH key](#generating-a-new-ssh-key). If you're unsure whether you already have an SSH key, check for [existing keys](/articles/checking-for-existing-ssh-keys).
|
||||
|
||||
@@ -7,6 +7,9 @@ redirect_from:
|
||||
- /articles/githubs-ssh-key-fingerprints
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
|
||||
|
||||
@@ -17,6 +17,12 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
- identity
|
||||
- access management
|
||||
- usernames
|
||||
- device verification
|
||||
---
|
||||
|
||||
|
||||
|
||||
@@ -8,5 +8,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
|
||||
@@ -10,5 +10,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
|
||||
@@ -6,6 +6,9 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
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.
|
||||
|
||||
@@ -8,6 +8,8 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
@@ -9,6 +9,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
{% mac %}
|
||||
|
||||
@@ -10,6 +10,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
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.
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
### Reviewing your authorized {% data variables.product.prodname_oauth_app %}s
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
|
||||
@@ -8,6 +8,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
### Accessing your security log
|
||||
|
||||
@@ -9,6 +9,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
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.
|
||||
|
||||
@@ -9,5 +9,7 @@ mapTopic: true
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- 2fa
|
||||
---
|
||||
|
||||
|
||||
@@ -9,6 +9,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
{% data reusables.gpg.desktop-support-for-commit-signing %}
|
||||
|
||||
|
||||
@@ -8,6 +8,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
{% data reusables.gpg.desktop-support-for-commit-signing %}
|
||||
|
||||
@@ -6,6 +6,9 @@ redirect_from:
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
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.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Telling Git about your signing key
|
||||
intro: "To sign commits locally, you need to inform Git that there's a GPG or X.509 key you'd like to use."
|
||||
intro: 'To sign commits locally, you need to inform Git that there''s a GPG or X.509 key you''d like to use.'
|
||||
redirect_from:
|
||||
- /articles/telling-git-about-your-gpg-key/
|
||||
- /articles/telling-git-about-your-signing-key
|
||||
@@ -8,6 +8,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
{% mac %}
|
||||
|
||||
@@ -7,6 +7,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
Before testing your SSH connection, you should have:
|
||||
|
||||
@@ -9,5 +9,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
|
||||
@@ -8,5 +8,7 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
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.
|
||||
|
||||
@@ -9,6 +9,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
{% if currentVersion != "github-ae@latest" %}
|
||||
|
||||
@@ -7,6 +7,9 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- identity
|
||||
- access management
|
||||
---
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
@@ -5,6 +5,8 @@ redirect_from:
|
||||
- /articles/using-ssh-over-the-https-port
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- ssh
|
||||
---
|
||||
|
||||
{% tip %}
|
||||
|
||||
@@ -5,6 +5,8 @@ redirect_from:
|
||||
- /articles/viewing-and-managing-your-active-saml-sessions
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- sso
|
||||
---
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
@@ -24,4 +26,4 @@ versions:
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[About authentication with SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)"
|
||||
- "[About authentication with SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)"
|
||||
|
||||
@@ -9,6 +9,8 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user