Reviewing your SSH keys

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.

No canto superior direito de qualquer página, clique na foto do seu perfil e em Configurações.
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.
Inicie o ssh-agent em segundo plano.
```
$ eval "$(ssh-agent -s)"
> Agent pid 59566
```
Dependendo do seu ambiente, talvez seja necessário usar um comando diferente. Por exemplo, talvez seja necessário usar o acesso raiz executando sudo -s -H antes de iniciar o ssh-agent ou usar exec ssh-agent bash ou exec ssh-agent zsh para executar o ssh-agent.

Find and take a note of your public key fingerprint.

$ ssh-add -l -E sha256
> 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA)

The SSH keys on GitHub Enterprise Server should match the same keys on your computer.

No canto superior direito de qualquer página, clique na foto do seu perfil e em Configurações.
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.

Se você estiver usando o Git Bash, ative o ssh-agent:

# start the ssh-agent in the background
$ eval "$(ssh-agent -s)"
> Agent pid 59566

Se você estiver usando outro prompt de terminal, como o Git para Windows, ative o 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.

$ ssh-add -l -E sha256
> 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA)

The SSH keys on GitHub Enterprise Server should match the same keys on your computer.

No canto superior direito de qualquer página, clique na foto do seu perfil e em Configurações.
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.
Inicie o ssh-agent em segundo plano.
```
$ eval "$(ssh-agent -s)"
> Agent pid 59566
```
Dependendo do seu ambiente, talvez seja necessário usar um comando diferente. Por exemplo, talvez seja necessário usar o acesso raiz executando sudo -s -H antes de iniciar o ssh-agent ou usar exec ssh-agent bash ou exec ssh-agent zsh para executar o ssh-agent.

Find and take a note of your public key fingerprint.

$ ssh-add -l -E sha256
> 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA)

The SSH keys on GitHub Enterprise Server should match the same keys on your computer.

Warning: If you see an SSH key you're not familiar with on GitHub Enterprise Server, delete it immediately and contact seu administrador do site for further help. An unidentified public key may indicate a possible security concern.