Please follow the instructions on this page:
There is another website, but it doesn't use SSL / HTTPS:
The procedure is the same as I have already described for CentOS or Debian in my previous posts:
- Import the GPG-key and verify its fingerprint.
- Download the checksum file and verify its signature with the GPG-key.
- Check the iso file with the checksum file.
Again the fingerprint of the GPG-key is on a SSL encrypted website where you have to check the website certificate and its root CA.
Firefox ships with its own set of root CAs ("Builtin Object Token" as the Security Device in advanced preference settings). Here is a list of all root CAs included in Firefox along with their fingerprints:
Builtin root CAs are hardcoded in /usr/lib/firefox/libnssckbi.so
CAs marked as "Software Security Device" are usually intermediate certificates that are downloaded from websites and stored locally. These CAs that are not builtin are either stored on a PKCS#11 compatible smartcard attached to your PC/laptop or saved to your home directory:
certutil -d ~/.mozilla/firefox/xxx.default -L
Chromium / Google Chrome does not ship with its own CA list but uses the CAs from the underlying operating system:
On Ubuntu 16.04 these CAs are hardcoded in /usr/lib/x86_64-linux-gnu/nss/libnssckbi.so which is part of the package "libnss3".
Important things to note:
- Verification of ISO images is based on GPG-keys which have to be checked by its fingerprints. You can get that fingerprint from a SSL secured website.
- The security of a website depends on the root CA which is used to sign the website certificate. These CAs are stored locally in different locations based on the browser you are using.
- Neither Firefox nor Chromium / Google Chrome are using CAs from the package "ca-certificates".