Skip to content

Commit 845d0a5

Browse files
authored
Merge pull request #22418 from github/repo-sync
repo sync
2 parents a658163 + 39549ab commit 845d0a5

File tree

2 files changed

+14
-5
lines changed

2 files changed

+14
-5
lines changed

content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,16 @@ shortTitle: SSH key fingerprints
1818
These are {% data variables.product.prodname_dotcom %}'s public key fingerprints:
1919

2020
- `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA)
21+
- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA - deprecated)
2122
- `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA)
2223
- `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU` (Ed25519)
2324

24-
For more information, see [Get Meta Information](/rest/meta#get-github-meta-information).
25+
You can add the following ssh key entries to your `~.ssh/known_hosts` file to avoid manually verifying {% data variables.product.prodname_dotcom %} hosts:
26+
27+
```text
28+
github.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl
29+
github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEmKSENjQEezOmxkZMy7opKgwFB9nkt5YRrYMjNuG5N87uRgg6CLrbo5wAdT/y6v0mKV0U2w0WZ2YB/++Tpockg=
30+
github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
31+
```
32+
33+
For more information, see "[Get {% data variables.product.prodname_dotcom %} Meta Information](/rest/meta#get-github-meta-information)."

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ $ ssh -T -p 443 [email protected]
3030
3131
**Note**: The hostname for port 443 is `ssh.{% data variables.command_line.backticks %}`, not `{% data variables.command_line.backticks %}`.
3232
33-
{% endnote %}
33+
{% endnote %}
3434
3535
If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey).
3636
@@ -71,8 +71,8 @@ that the host wasn't found in `known_hosts`, or that it was found by another nam
7171
> ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU.
7272
> This host key is known by the following other names/addresses:
7373
> ~/.ssh/known_hosts:32: github.com
74-
> Are you sure you want to continue connecting (yes/no/[fingerprint])?
74+
> Are you sure you want to continue connecting (yes/no/[fingerprint])?
7575
```
7676

77-
It is safe to answer `yes` to this question, assuming that the SSH fingerprint matches
78-
one of GitHub's published fingerprints. For more information, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)."
77+
It is safe to answer "yes" to this question, assuming that the SSH fingerprint matches
78+
one of GitHub's published fingerprints. For the list of fingerprints, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)."

0 commit comments

Comments
 (0)