jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

correct internal redirecting links (authentication/troubleshooting) (#34458)

Browse Source
This commit is contained in:
Peter Bengtsson
2023-02-09 10:03:50 -05:00
committed by GitHub
parent ac24b99c00
commit a7dd99d19a
12 changed files with 30 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md
View File

@@ -43,6 +43,6 @@ shortTitle: Check verification status
## Further reading
- "[About commit signature verification](/articles/about-commit-signature-verification)"
- "[Signing commits](/articles/signing-commits)"
- "[Signing tags](/articles/signing-tags)"
- "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)"
- "[Signing commits](/authentication/managing-commit-signature-verification/signing-commits)"
- "[Signing tags](/authentication/managing-commit-signature-verification/signing-tags)"

6
content/authentication/troubleshooting-commit-signature-verification/using-a-verified-email-address-in-your-gpg-key.md
View File

@@ -16,12 +16,12 @@ topics:
shortTitle: Use verified email in GPG key
---
{% ifversion fpt or ghec %}
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)."
If you need to verify your GitHub email address, see "[Verifying your email address](/get-started/signing-up-for-github/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](/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key)."
Commits and tags may contain several email addresses. For commits, there is the author — the person who wrote the code — and the committer — the person who added the commit to the tree. When signing a commit with Git, whether it be during a merge, cherry-pick, or normal `git commit`, the committer email address will be yours, even if the author email address isn't. Tags are more simple: The tagger email address is always the user who created the tag.
If you need to change your committer or tagger email address, see "[Setting your commit email address](/articles/setting-your-commit-email-address/)."
If you need to change your committer or tagger email address, see "[Setting your commit email address](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address)."
## Further reading
- "[About commit signature verification](/articles/about-commit-signature-verification)"
- "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)"

4
content/authentication/troubleshooting-ssh/deleted-or-missing-ssh-keys.md
View File

@@ -14,6 +14,6 @@ shortTitle: Deleted or missing SSH keys
---
{% 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/)."
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](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)."
After your inactive SSH key is deleted, you must generate a new SSH key and associate it with your account. For more information, 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/)" and "[Adding a new SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account/)."
After your inactive SSH key is deleted, you must generate a new SSH key and associate it with your account. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your GitHub account](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)."

6
content/authentication/troubleshooting-ssh/error-bad-file-number.md
View File

@@ -28,7 +28,7 @@ $ ssh -vT git@{% data variables.command_line.codeblock %}
### Use HTTPS
Often, the simplest solution is to simply avoid SSH entirely. Most firewalls and proxies allow HTTPS traffic without issue. To take advantage of this, change [the remote URL](/github/getting-started-with-github/about-remote-repositories) you're using:
Often, the simplest solution is to simply avoid SSH entirely. Most firewalls and proxies allow HTTPS traffic without issue. To take advantage of this, change [the remote URL](/get-started/getting-started-with-git/about-remote-repositories) you're using:
```shell
$ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPO-NAME.git
@@ -47,7 +47,7 @@ If you can connect the computer to another network that doesn't have a firewall,
### Using SSH over the HTTPS port
If using HTTPS is not an option, and your firewall admin refuses to allow SSH connections, you can try using [SSH over the HTTPS port](/articles/using-ssh-over-the-https-port) instead.
If using HTTPS is not an option, and your firewall admin refuses to allow SSH connections, you can try using [SSH over the HTTPS port](/authentication/troubleshooting-ssh/using-ssh-over-the-https-port) instead.
{% endif %}
@@ -55,6 +55,6 @@ If using HTTPS is not an option, and your firewall admin refuses to allow SSH co
## Further reading
- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)"
- "[Troubleshooting connectivity problems](/get-started/using-github/troubleshooting-connectivity-problems)"
{% endif %}

8
content/authentication/troubleshooting-ssh/error-key-already-in-use.md
View File

@@ -24,7 +24,7 @@ $ ssh -T -ai ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %}
> provide shell access.
```
The *username* in the response is the account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} that the key is currently attached to. If the response looks something like "username/repo", the key has been attached to a repository as a [*deploy key*](/guides/managing-deploy-keys#deploy-keys).
The *username* in the response is the account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} that the key is currently attached to. If the response looks something like "username/repo", the key has been attached to a repository as a [*deploy key*](/developers/overview/managing-deploy-keys#deploy-keys).
To force SSH to use only the key provided on the command line, use `-o` to add the `IdentitiesOnly=yes` option:
@@ -35,10 +35,10 @@ $ ssh -v -o "IdentitiesOnly=yes" -i ~/.ssh/id_rsa git@{% data variables.command_
## Fixing the issue
To resolve the issue, first remove the key from the other account or repository and then [add it to your account](/articles/adding-a-new-ssh-key-to-your-github-account).
To resolve the issue, first remove the key from the other account or repository and then [add it to your account](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account).
If you don't have permissions to transfer the key, and can't contact a user who does, remove the keypair and [generate a brand new one](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent).
If you don't have permissions to transfer the key, and can't contact a user who does, remove the keypair and [generate a brand new one](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent).
## Deploy keys
Once a key has been attached to one repository as a deploy key, it cannot be used on another repository. If you're running into this error while setting up deploy keys, see "[Managing deploy keys](/guides/managing-deploy-keys)."
Once a key has been attached to one repository as a deploy key, it cannot be used on another repository. If you're running into this error while setting up deploy keys, see "[Managing deploy keys](/developers/overview/managing-deploy-keys)."

12
content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md
View File

@@ -16,7 +16,7 @@ shortTitle: Permission denied (publickey)
---
## Should the `sudo` command or elevated privileges be used with Git?
You should not be using the `sudo` command or elevated privileges, such as administrator permissions, 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.
You should not be using the `sudo` command or elevated privileges, such as administrator permissions, 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](/authentication/connecting-to-github-with-ssh) without `sudo` and then try to use a command like `sudo git push`, you won't be using the same keys that you generated.
## Check that you are connecting to the correct server
@@ -33,7 +33,7 @@ $ ssh -vT git@{% data variables.command_line.codeblock %}
> debug1: Connecting to {% data variables.command_line.codeblock %} port 22.
```
The connection should be made on port 22{% ifversion fpt or ghec %}, unless you're overriding settings to use [SSH over HTTPS](/articles/using-ssh-over-the-https-port){% endif %}.
The connection should be made on port 22{% ifversion fpt or ghec %}, unless you're overriding settings to use [SSH over HTTPS](/authentication/troubleshooting-ssh/using-ssh-over-the-https-port){% endif %}.
## Always use the "git" user
@@ -43,7 +43,7 @@ All connections, including those for remote URLs, must be made as the "git" user
$ ssh -T GITHUB-USERNAME@{% data variables.command_line.codeblock %}
> Permission denied (publickey).
```
If your connection failed and you're using a remote URL with your {% data variables.product.product_name %} username, you can [change the remote URL to use the "git" user](/github/getting-started-with-github/managing-remote-repositories).
If your connection failed and you're using a remote URL with your {% data variables.product.product_name %} username, you can [change the remote URL to use the "git" user](/get-started/getting-started-with-git/managing-remote-repositories).
You should verify your connection by typing:
@@ -95,7 +95,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
{% endlinux %}
The `ssh-add` command *should* print out a long string of numbers and letters. If it does not print anything, you will need to [generate a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) and associate it with {% data variables.product.product_name %}.
The `ssh-add` command *should* print out a long string of numbers and letters. If it does not print anything, you will need to [generate a new SSH key](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) and associate it with {% data variables.product.product_name %}.
{% tip %}
@@ -208,10 +208,10 @@ You must provide your public key to {% data variables.product.product_name %} to
{% endlinux %}
If you don't see your public key in {% data variables.product.product_name %}, you'll need to [add your SSH key to {% data variables.product.product_name %}](/articles/adding-a-new-ssh-key-to-your-github-account) to associate it with your computer.
If you don't see your public key in {% data variables.product.product_name %}, you'll need to [add your SSH key to {% data variables.product.product_name %}](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) to associate it with your computer.
{% warning %}
**Warning**: If you see an SSH key you're not familiar with on {% data variables.product.product_name %}, delete it immediately and contact {% data variables.contact.contact_support %}, for further help. An unidentified public key may indicate a possible security concern. For more information, see "[Reviewing your SSH keys](/articles/reviewing-your-ssh-keys)."
**Warning**: If you see an SSH key you're not familiar with on {% data variables.product.product_name %}, delete it immediately and contact {% data variables.contact.contact_support %}, for further help. An unidentified public key may indicate a possible security concern. For more information, see "[Reviewing your SSH keys](/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys)."
{% endwarning %}

4
content/authentication/troubleshooting-ssh/error-permission-to-userrepo-denied-to-userother-repo.md
View File

@@ -15,6 +15,6 @@ topics:
- SSH
shortTitle: Permission denied other-repo
---
To fix this, remove the deploy key from the repository, and [add the key to your personal account](/articles/adding-a-new-ssh-key-to-your-github-account) instead.
To fix this, remove the deploy key from the repository, and [add the key to your personal account](/authentication/connecting-to-github-with-ssh/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.
If the key you are using is intended to be a deploy key, check out [our guide on deploy keys](/developers/overview/managing-deploy-keys) for more details.

2
content/authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k.md
View File

@@ -33,6 +33,6 @@ To add your SSH private key to the ssh-agent, you can specify the path to the Ap
## Further reading
- "[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)"
- "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)"
- [Linux man page for SSH-ADD](http://man7.org/linux/man-pages/man1/ssh-add.1.html)
- To view Apple's man page for SSH-ADD, run `man ssh-add` in Terminal

2
content/authentication/troubleshooting-ssh/error-unknown-key-type.md
View File

@@ -33,6 +33,6 @@ If you remove OpenSSH, the passphrases that are stored in your keychain will onc
1. Open Terminal.
2. Enter the command `brew install openssh`.
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)."
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](/authentication/connecting-to-github-with-ssh/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 %}

2
content/authentication/troubleshooting-ssh/error-were-doing-an-ssh-key-audit.md
View File

@@ -27,4 +27,4 @@ fatal: could not read from remote repository
```
## Solving the issue
To fix this, you need to [review your SSH keys](/articles/reviewing-your-ssh-keys) and either reject or approve the unverified key. Clicking the URL link in the error message brings you to the SSH Settings page, where the unverified SSH key is highlighted in the SSH key list.
To fix this, you need to [review your SSH keys](/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys) and either reject or approve the unverified key. Clicking the URL link in the error message brings you to the SSH Settings page, where the unverified SSH key is highlighted in the SSH key list.

6
content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
View File

@@ -18,7 +18,7 @@ shortTitle: Recover SSH key passphrase
---
{% 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.
If you [configured your SSH passphrase with the macOS keychain](/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), you may be able to recover it.
1. In Finder, search for the **Keychain Access** app.
![Spotlight Search bar](/assets/images/help/setup/keychain-access.png)
@@ -33,12 +33,12 @@ If you [configured your SSH passphrase with the macOS keychain](/articles/workin
{% windows %}
If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/github/getting-started-with-github/about-remote-repositories#cloning-with-https-urls) so you can use a {% data variables.product.pat_generic %} instead.
If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls) so you can use a {% data variables.product.pat_generic %} instead.
{% endwindows %}
{% linux %}
If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/github/getting-started-with-github/about-remote-repositories#cloning-with-https-urls) so you can use a {% data variables.product.pat_generic %} instead.
If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls) so you can use a {% data variables.product.pat_generic %} instead.
{% endlinux %}

2
content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
View File

@@ -32,7 +32,7 @@ $ ssh -T -p 443 git@ssh.github.com
{% endnote %}
If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey).
If that worked, great! If not, you may need to [follow our troubleshooting guide](/authentication/troubleshooting-ssh/error-permission-denied-publickey).
Now, to clone the repository, you can run the following command: