This version of GitHub Enterprise will be discontinued on
This version of GitHub Enterprise was discontinued on
2020-05-23.
No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise.
For help with the upgrade, contact GitHub Enterprise support.
To keep your credentials secure, you should regularly audit your SSH keys, deploy keys, and review authorized applications that access your GitHub Enterprise account.
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.
In the upper-right corner of any page, click your profile photo, then click Settings.
In the user settings sidebar, click SSH and GPG keys.
On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click Delete. If there are valid SSH keys you'd like to keep, click Approve.
Note: If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the SSH key audit error will be highlighted in the list of SSH keys.
Open Terminal.
Start the ssh-agent in the background.
$ eval "$(ssh-agent -s)"
> Agent pid 59566
Find and take a note of your public key fingerprint. If you're using OpenSSH 6.7 or older:
The SSH keys on GitHub Enterprise should match the same keys on your computer.
In the upper-right corner of any page, click your profile photo, then click Settings.
In the user settings sidebar, click SSH and GPG keys.
On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click Delete. If there are valid SSH keys you'd like to keep, click Approve.
Note: If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the SSH key audit error will be highlighted in the list of SSH keys.
Open Git Bash. If you're using Git Shell, which is included in GitHub Desktop, open Git Shell and skip to step 6.
If you are using Git Bash, turn on ssh-agent:
# start the ssh-agent in the background
$ eval "$(ssh-agent -s)"
> Agent pid 59566
If you are using another terminal prompt, such as Git for Windows, turn on ssh-agent:
# start the ssh-agent in the background
$ eval $(ssh-agent -s)
> Agent pid 59566
Find and take a note of your public key fingerprint. If you're using OpenSSH 6.7 or older:
The SSH keys on GitHub Enterprise should match the same keys on your computer.
In the upper-right corner of any page, click your profile photo, then click Settings.
In the user settings sidebar, click SSH and GPG keys.
On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click Delete. If there are valid SSH keys you'd like to keep, click Approve.
Note: If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the SSH key audit error will be highlighted in the list of SSH keys.
Open Terminal.
Start the ssh-agent in the background.
$ eval "$(ssh-agent -s)"
> Agent pid 59566
Find and take a note of your public key fingerprint. If you're using OpenSSH 6.7 or older:
The SSH keys on GitHub Enterprise should match the same keys on your computer.
Warning: If you see an SSH key you're not familiar with on GitHub Enterprise, delete it immediately and contact your GitHub Enterprise site administrator for further help. An unidentified public key may indicate a possible security concern.
