1.0

Download Tails 3.7.1

Direct download

1.2Verify your download using your browser

For your security,
always verify your download!

X

With an unverified download, you might:

How does the extension work?

Our browser extension makes it quick and easy.

Our browser extension is broken in Tails 3.6 and 3.6.1. Please use it from Firefox, Chrome, or Tor Browser outside of Tails.

Install Tails Verification extension Install Tails Verification extension

You seem to have JavaScript disabled. To use our browser extension, please allow all this page:

Your extension is an older version.

Update extension Update extension

Tails Verification extension installed!

Verifying $FILENAME

Verification successful!

Verification failed!

X

Most likely, the verification failed because of an error or interruption during the download.

The verification also fails if you try to verify a different download than the latest version ( 3.7.1 ).

Less likely, the verification might have failed because of a malicious download from our download mirrors or due to a network attack in your country or local network.

Downloading again is usually enough to fix this problem.

How does the extension work?

Please try to download again…

Verification failed again!

X

The verification might have failed again because of:

  • A software problem in our verification extension
  • A malicious download from our download mirrors
  • A network attack in your country or local network

Trying from a different place or a different computer might solve any of these issues.

Please try to download again from a different place or a different computer…

1.3Continue installing upgrading installing or upgrading

You are using $DETECTED-BROWSER.

Direct download is only available for:

  • Firefox $MINVER-FIREFOX and later (Download)
  • Chrome$MINVER-CHROME and later (Download)
  • Tor Browser $MINVER-TOR-BROWSER and later (Download)

Please update your browser to the latest version.

For your security,
always verify your download!

X

With an unverified download, you might:

How does the extension work?

Our browser extension for Firefox, Chrome, and Tor Browser makes this quick and easy.

Copy and paste this link in Firefox, Chrome, or Tor Browser:

https://tails.boum.org/install/debian/usb-download/

https://tails.boum.org/install/win/usb-download/

https://tails.boum.org/install/linux/usb-download/

https://tails.boum.org/install/mac/usb-download/

https://tails.boum.org/install/mac/dvd-download/

https://tails.boum.org/upgrade/tails-download/

https://tails.boum.org/install/dvd-download/

https://tails.boum.org/install/vm-download/

https://tails.boum.org/install/download/

BitTorrent download

X

BitTorrent is a peer-to-peer technology for file sharing that makes your download faster and easier to resume.

You need to install BitTorrent software on your computer, like Transmission (for Windows, macOS, and Linux).

BitTorrent doesn't work over Tor or in Tails.

1.1Download Tails (Torrent file)

Download Tails 3.7.1 Torrent file

1.2Verify your download using BitTorrent

Your BitTorrent client will automatically verify your download when it is complete.

1.3Continue installing upgrading installing or upgrading

Open and download the Torrent file with your BitTorrent client. It contains the Tails 3.7.1 ISO image that you will use in the next step.

Verify using OpenPGP (optional)

If you know OpenPGP, you can also verify your download using an OpenPGP signature instead of, or in addition to, our browser extension or BitTorrent.

  1. Download the Tails signing key.

  2. Download the Tails 3.7.1 OpenPGP signature and save it to the same folder where you saved the ISO image.

Basic OpenPGP verification

See instructions for basic OpenPGP verification.

This section provides simplified instructions:

In Windows with Gpg4win

See the Gpg4win documentation on verifying signatures.

Verify that the date of the signature is at most five days earlier than the latest version: 2018-06-10.

If the following warning appears:

Not enough information to check the signature validity.
Signed on ... by tails@boum.org (Key ID: 0x58ACD84F
The validity of the signature cannot be verified.

Then the ISO image is still correct according to the signing key that you downloaded. To remove this warning you need to authenticate the signing key through the OpenPGP Web of Trust.

In macOS using GPGTools

  1. Open Finder and navigate to the folder where you saved the ISO image and the signature.
  2. Right-click on the ISO image and choose ServicesOpenPGP: Verify Signature of File.

In Tails

  1. Open the file browser and navigate to the folder where you saved the ISO image and the signature.
  2. Right-click on the signature and choose Open With Verify Signature.
  3. The verification of the ISO image starts automatically:

  4. After the verification finishes, you should see a notification that the signature is good:

    Verify that the date of the signature is at most five days earlier than the latest version: 2018-06-10.

Using the command line

  1. Open a terminal and navigate to the folder where you saved the ISO image and the signature.
  2. Execute:

    gpg --no-options --keyid-format 0xlong --verify tails-amd64-3.7.1.iso.sig tails-amd64-3.7.1.iso

    The output of this command should be the following:

    gpg: Signature made Sat 09 Jun 2018 08:54:10 PM UTC
    gpg:                using EDDSA key CD4D4351AFA6933F574A9AFB90B2B4BD7AED235F
    gpg: checking the trustdb
    gpg: marginals needed: 3  completes needed: 1  trust model: pgp
    gpg: depth: 0  valid:  21  signed:  68  trust: 0-, 0q, 0n, 0m, 0f, 21u
    gpg: depth: 1  valid:  68  signed: 388  trust: 9-, 6q, 1n, 52m, 0f, 0u
    gpg: depth: 2  valid: 161  signed: 400  trust: 48-, 58q, 1n, 53m, 1f, 0u
    gpg: depth: 3  valid: 132  signed: 277  trust: 83-, 28q, 3n, 18m, 0f, 0u
    gpg: depth: 4  valid:  14  signed:  78  trust: 10-, 0q, 0n, 4m, 0f, 0u
    gpg: next trustdb check due at 2018-06-10
    gpg: Good signature from "Tails developers <tails@boum.org>" [full]
    gpg:                 aka "Tails developers (offline long-term identity key) <tails@boum.org>" [full]

    Verify that the date of the signature is at most five days earlier than the latest version: 2018-06-10.

    If the output also includes:

    gpg: WARNING: This key is not certified with a trusted signature!
    gpg: There is no indication that the signature belongs to the owner.

    Then the ISO image is still correct according to the signing key that you downloaded. To remove this warning you need to authenticate the signing key through the OpenPGP Web of Trust.

Authenticate the signing key through the OpenPGP Web of Trust

Authenticating our signing key through the OpenPGP Web of Trust is the only way that you can be protected in case our website is compromised or if you are a victim of a man-in-the-middle attack. However, it is complicated to do and it might not be possible for everyone because it relies on trust relationships between individuals.

Read more about authenticating the Tails signing key through the OpenPGP Web of Trust.

The verification techniques that we present (browser extension, BitTorrent, or OpenPGP verification) all rely on some information being securely downloaded using HTTPS from our website:

  • The checksum for the Firefox extension
  • The Torrent file for BitTorrent
  • The Tails signing key for OpenPGP verification

It is possible that you could download malicious information if our website is compromised or if you are a victim of a man-in-the-middle attack.

OpenPGP verification is the only technique that protects you if our website is compromised or if you are a victim of a man-in-the-middle attack. But, for that you need to authenticate the Tails signing key through the OpenPGP Web of Trust.

If you are verifying an ISO image from inside Tails, for example, to do a manual upgrade, then you already have the Tails signing key. You can trust this signing key as much as you already trust your Tails installation since this signing key is included in your Tails installation.

One of the inherent problems of standard HTTPS is that the trust put in a website is defined by certificate authorities: a hierarchical and closed set of companies and governmental institutions approved by your web browser vendor. This model of trust has long been criticized and proved several times to be vulnerable to attacks as explained on our warning page.

We believe that, instead, users should be given the final say when trusting a website, and that designation of trust should be done on the basis of human interactions.

The OpenPGP Web of Trust is a decentralized trust model based on OpenPGP keys that can help with solving this problem. Let's see this with an example:

  1. You are friends with Alice and you really trust her way of making sure that OpenPGP keys actually belong to their owners.
  2. Alice met Bob, a Tails developer, in a conference and certified Bob's key as actually belonging to Bob.
  3. Bob is a Tails developer who directly owns the Tails signing key. So, Bob has certified the Tails signing key as actually belonging to Tails.

In this scenario, you found, through Alice and Bob, a path to trust the Tails signing key without the need to rely on certificate authorities.

If you are on Debian, Ubuntu, or Linux Mint, you can install the debian-keyring package which contains the OpenPGP keys of all Debian developers. Some Debian developers have certified the Tails signing key and you can use these certifications to build a trust path. This technique is explained in detail in our instructions on installing Tails from Debian, Ubuntu, or Linux Mint using the command line.

Relying on the Web of Trust requires both caution and intelligent supervision by the users. The technical details are outside of the scope of this document.

Since the Web of Trust is based on actual human relationships and real-life interactions, it is best to get in touch with people knowledgeable about OpenPGP and build trust relationships in order to find your own trust path to the Tails signing key.

For example, you can start by contacting a local Linux User Group, an organization offering Tails training, or other Tails enthusiasts near you and exchange about their OpenPGP practices.

After you build a trust path, you can certify the Tails signing key by signing it with your own key to get rid of some warnings during the verification process.