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.
-
En la esquina superior derecha de cualquier página, da clic en tu foto de perfil y después da clic en Configuración.
-
En la barra lateral de configuración de usuario, da clic en Llaves SSH y GPG.
-
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.
-
Inicia el agente SSH en segundo plano.
$ 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:
$ ssh-add -l > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA)If you're using OpenSSH 6.8 or newer:
$ ssh-add -l -E md5 > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA)
- The SSH keys on GitHub Enterprise should match the same keys on your computer.
-
En la esquina superior derecha de cualquier página, da clic en tu foto de perfil y después da clic en Configuración.
-
En la barra lateral de configuración de usuario, da clic en Llaves SSH y GPG.
-
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.
-
Si estás usando Git Bash, activa el ssh-agent:
# inicia el ssh-agent en segundo plano $ eval "$(ssh-agent -s)" > Agent pid 59566Si estás usando otro símbolo de terminal, como Git para Windows, activa el 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:
$ ssh-add -l > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA)If you're using OpenSSH 6.8 or newer:
$ ssh-add -l -E md5 > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA)
- The SSH keys on GitHub Enterprise should match the same keys on your computer.
-
En la esquina superior derecha de cualquier página, da clic en tu foto de perfil y después da clic en Configuración.
-
En la barra lateral de configuración de usuario, da clic en Llaves SSH y GPG.
-
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.
-
Inicia el agente SSH en segundo plano.
$ 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:
$ ssh-add -l > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA)If you're using OpenSSH 6.8 or newer:
$ ssh-add -l -E md5 > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA)
- 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 tu administrador del sitio empresarial GitHub for further help. An unidentified public key may indicate a possible security concern.