Attention: These instructions are to verify the tor source code.
Please follow the right instructions to verify Tor Browser's signature.
A assinatura digital é um processo que assegura que um certo pacote foi gerado pelos seus programadores e que não foi manipulado.
Below we explain why it is important and how to verify that the tor source code you download is the one we have created and has not been modified by some attacker.
Each file on our download page is accompanied by two files which are labelled "checksum" and "sig" with the same name as the package and the extension ".sha256sum" and ".sha256sum.asc" respectively.
The .asc file will verify that the .sha256sum file (containing the checksum of the package) has not been tampered with. Once the signature has been validated (see below on how to do it), the package integrity can be validated with:
$ sha256sum -c *.sha256sum
These files allow you to verify the file you've downloaded is exactly the one that we intended you to get.
This will vary by web browser, but generally you can download this file by right-clicking the "sig" and "checksum" link and selecting the "save file as" option.
For example, tor-0.4.6.7.tar.gz is accompanied by tor-0.4.6.7.tar.gz.sha256sum.asc.
These are example file names and will not exactly match the file names that you download.
Agora nós vamos mostrar-lhe como pode verificar a assinatura digital do ficheiro transferido em vários sistemas operativos.
Por favor, note que a assinatura tem a mesma data em que o pacote foi assinado.
Por isso, de cada vez que um novo ficheiro é enviado, é gerada uma nova assinatura com uma data diferente.
Desde que tenha verificado a assinatura, não deve preocupar-se que estas datas não sejam iguais.
Instalação de GnuPG
Antes de mais, tem de instalar o GnuPG antes de poder verificar as assinaturas.
Para os utilizadores do Windows:
Se usar Windows, descarregue o Gpg4win e corra o seu instalador.
Para poder verificar a assinatura, terá de digitar uns comandos na linha de comandos do Windows, cmd.exe.
Para os utilizadores de macOS:
If you are using macOS, you can install GPGTools.
Para poder verificar a assinatura, terá de digitar uns comandos no Terminal (sob "Applications").
Para os utilizadores de GNU/Linux:
Se estiver a usar GNU/Linux, então provavelmente já tem o GnuPG no seu sistema, visto que a maioria das distribuições GNU/Linux vêm com o GnuPG pré-instalado.
In order to verify the signature you will need to type a few commands in a terminal window.
How to do this will vary depending on your distribution.
Obtendo a chave dos desenvolvedores do Tor
The following keys can sign the tarball. Don't expect them all, it can vary depending on who is available to make the release.
You can fetch the key with the links provided above or with:
$ gpg --auto-key-locate nodefault,wkd --locate-keys ahf@torproject.org
$ gpg --auto-key-locate nodefault,wkd --locate-keys dgoulet@torproject.org
$ gpg --auto-key-locate nodefault,wkd --locate-keys nickm@torproject.org
This should show you something like (for nickm):
gpg: key FE43009C4607B1FB: public key "Nick Mathewson <nickm@torproject.org>" imported
gpg: Número total processados: 1
gpg: imported: 1
pub rsa4096 2016-09-21 [C] [expires: 2025-10-04]
2133BC600AB133E1D826D173FE43009C4607B1FB
uid [ unknown] Nick Mathewson <nickm@torproject.org>
sub rsa4096 2016-09-23 [S] [expires: 2025-10-04]
sub rsa4096 2016-09-23 [E] [expires: 2025-10-04]
If you get an error message, something has gone wrong and you cannot continue until you've figured out why this didn't work.
You might be able to import the key using the Workaround (using a public key) section instead.
After importing the key, you can save it to a file (identifying it by its fingerprint here):
$ gpg --output ./tor.keyring --export 0x2133BC600AB133E1D826D173FE43009C4607B1FB
This command results in the key being saved to a file found at the path ./tor.keyring, i.e. in the current directory.
If ./tor.keyring doesn't exist after running this command, something has gone wrong and you cannot continue until you've figured out why this didn't work.
Verificação da assinatura
To verify the signature of the package you downloaded, you will need to download the corresponding .sha256sum.asc signature file and the .sha256sum file itself, and verify it with a command that asks GnuPG to verify the file that you downloaded.
Os exemplos abaixo assumem que descarregou estes dois ficheiros para a sua pasta de Downloads.
Note that these commands use example file names and yours will be different: you will have downloaded a different version than 9.0 and you may not have chosen the English (en-US) version.
Para os utilizadores do Windows:
gpgv --keyring .\tor.keyring Downloads\tor-0.4.6.10.tar.gz.sha256sum.asc Downloads\tor-0.4.6.10.tar.gz.sha256sum
Para os utilizadores de macOS:
gpgv --keyring ./tor.keyring ~/Downloads/tor-0.4.6.10.tar.gz.sha256sum.asc ~/Downloads/tor-0.4.6.10.tar.gz.sha256sum
For BSD/Linux users:
gpgv --keyring ./tor.keyring ~/Downloads/tor-0.4.6.10.tar.gz.sha256sum.asc ~/Downloads/tor-0.4.6.10.tar.gz.sha256sum
The result of the command should produce something like this (depending on which key signed it):
gpgv: Signature made Mon 16 Aug 2021 04:44:27 PM -03
gpgv: using RSA key 7A02B3521DC75C542BA015456AFEE6D49E92B601
gpgv: Good signature from "Nick Mathewson <nickm@torproject.org>"
If you get error messages containing 'No such file or directory', either something went wrong with one of the previous steps, or you forgot that these commands use example file names and yours will be a little different.
Também pode saber mais sobre o GnuPG.
Verifying checksum
Now that we validated the signatures of the checksum, we need to verify the integrity of the package.
Para os utilizadores do Windows:
certUtil -hashfile tor-0.4.6.10.tar.gz.sha256sum SHA256
Para os utilizadores de macOS:
shasum -a 256 tor-0.4.6.10.tar.gz.sha256sum
For BSD/Linux users:
sha256sum -c tor-0.4.6.10.tar.gz.sha256sum