Navigation

Verify Integrity of MongoDB Packages

The MongoDB release team digitally signs all software packages to certify that a particular MongoDB package is a valid and unaltered MongoDB release. Before installing MongoDB, you should validate the package using either the provided PGP signature or SHA-256 checksum.

PGP signatures provide the strongest guarantees by checking both the authenticity and integrity of a file to prevent tampering.

Cryptographic checksums only validate file integrity to prevent network transmission errors.

Verify Linux/macOS Packages

Use PGP/GPG

MongoDB signs each release branch with a different PGP key. The public key files for each release branch since MongoDB 2.2 are available for download from the key server in both textual .asc and binary .pub formats.

1

Download the MongoDB installation file.

Download the binaries from MongoDB Download Center based on your environment.

For example, to download the 4.0.20 release for macOS through the shell, run this command:

curl -LO https://fastdl.mongodb.org/osx/mongodb-osx-ssl-x86_64-4.0.20.tgz
2

Download the public signature file.

curl -LO https://fastdl.mongodb.org/osx/mongodb-osx-ssl-x86_64-4.0.20.tgz.sig
3

Download then import the key file.

If you have not downloaded and imported the MongoDB 4.0 public key, run these commands:

curl -LO https://www.mongodb.org/static/pgp/server-4.0.asc
gpg --import server-4.0.asc

PGP should return this response:

gpg: key 68818C72E52529D4: public key "MongoDB 4.0 Release Signing Key <packaging@mongodb.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1
4

Verify the MongoDB installation file.

Run this command:

gpg --verify mongodb-osx-ssl-x86_64-4.0.20.tgz.sig mongodb-osx-ssl-x86_64-4.0.20.tgz

GPG should return this response:

gpg: Signature made Thu Jul 25 01:20:01 2019 EDT
gpg:                using RSA key 68818C72E52529D4
gpg: Good signature from "MongoDB 4.0 Release Signing Key <packaging@mongodb.com>" [unknown]

If the package is properly signed, but you do not currently trust the signing key in your local trustdb, gpg will also return the following message:

gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 9DA3 1620 334B D75D 9DCB  49F3 6881 8C72 E525 29D4

If you receive a message this error message, confirm that you imported the correct public key:

gpg: Signature made Mon Sep 11 12:03:48 2017 EDT using RSA key BC711F9BA15703C6
gpg: Can't check signature: public key not found

Use SHA-256

1

Download the MongoDB installation file.

Download the binaries from MongoDB Download Center based on your environment.

For example, to download the 4.0.20 release for macOS through the shell, run this command:

curl -LO https://fastdl.mongodb.org/osx/mongodb-osx-ssl-x86_64-4.0.20.tgz
2

Download the SHA256 file.

curl -LO https://fastdl.mongodb.org/osx/mongodb-osx-ssl-x86_64-4.0.20.tgz.sha256
3

Use the SHA-256 checksum to verify the MongoDB package file.

Compute the checksum of the package file:

shasum -c mongodb-osx-ssl-x86_64-4.0.20.tgz.sha256

which should return the following if the checksum matched the downloaded package:

mongodb-osx-ssl-x86_64-4.0.20.tgz: OK

Verify Windows Packages

This verifies the MongoDB binary against its SHA256 key.

1

Download the installer.

Download the MongoDB .msi installer. For example, to download the latest version of MongoDB Community Edition:

MongoDB Community Download Center

  1. In the Version dropdown, select 4.0.20 (current release).
  2. In the Platform dropdown, select Windows.
  3. In the Package dropdown, select msi.
  4. Click Download and save the file to your Downloads folder.
2

Get the public signature file.

Get the public signature file for your MongoDB version.

For example, for the SHA256 signature of the latest version of MongoDB Community Edition:

  1. From https://fastdl.mongodb.org/win32/mongodb-win32-x86_64-2008plus-ssl-4.0.20-signed.msi.sha256, copy the content.
  2. Save the content to a file mongodb-win32-x86_64-2008plus-ssl-4.0.20-signed.msi.sha256 in your Downloads folder.
3

Compare the signature file to the MongoDB installer hash.

To compare the signature file to the hash of the MongoDB binary, invoke this Powershell script:

$sigHash = (Get-Content $Env:HomePath\Downloads\mongodb-win32-x86_64-2008plus-ssl-4.0.20-signed.msi.sha256 | Out-String).SubString(0,64).ToUpper(); `
$fileHash = (Get-FileHash $Env:HomePath\Downloads\mongodb-win32-x86_64-2008plus-ssl-4.0.20-signed.msi).Hash.Trim(); `
echo $sigHash; echo $fileHash; `
$sigHash -eq $fileHash
0147CA4AAE70B6563B6703B720D982BF3B85533F9FB4E42E0D7F14CF690BA271
0147CA4AAE70B6563B6703B720D982BF3B85533F9FB4E42E0D7F14CF690BA271
True

The command outputs three lines:

  • A SHA256 hash that you downloaded directly from MongoDB.
  • A SHA256 hash computed from the MongoDB binary you downloaded from MongoDB.
  • A True or False result depending if the hashes match.

If the hashes match, the MongoDB binary is verified.