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.2.0 release for macOS through the shell, run this command:

curl -LO https://fastdl.mongodb.org/osx/mongodb-macos-x86_64-4.2.0.tgz
2

Download the public signature file.

curl -LO https://fastdl.mongodb.org/osx/mongodb-macos-x86_64-4.2.0.tgz.sig
3

Download then import the key file.

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

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

PGP should return this response:

gpg: key 4B7C549A058F8B6B: "MongoDB 4.2 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-macos-x86_64-4.2.0.tgz.sig mongodb-macos-x86_64-4.2.0.tgz

GPG should return this response:

gpg: Signature made Wed Jun  5 03:17:20 2019 EDT
gpg:                using RSA key 4B7C549A058F8B6B
gpg: Good signature from "MongoDB 4.2 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: E162 F504 A20C DF15 827F  718D 4B7C 549A 058F 8B6B

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

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.2.0 release for macOS through the shell, type this command:

curl -LO https://fastdl.mongodb.org/osx/mongodb-macos-x86_64-4.2.0.tgz
2

Download the SHA256 file.

curl -LO https://fastdl.mongodb.org/osx/mongodb-macos-x86_64-4.2.0.tgz.sha256
3

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

Compute the checksum of the package file:

shasum -c mongodb-macos-x86_64-4.2.0.tgz.sha256

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

mongodb-macos-x86_64-4.2.0.tgz: OK

Verify Windows Packages

This verifies the MongoDB binary against its SHA256 key.

1

Download the MongoDB .msi installation file.

Download the .msi from the MongoDB Download Center.

For example to download the latest 4.2 of MongoDB Community Edition, from the MongoDB Download Center:

  1. In the Version dropdown, select the version that corresponds to the latest MongoDB Server 4.2.
  2. In the OS dropdown, Windows 64-bit X64 should be selected.
  3. In the Package drop down, MSI should be selected.
  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 for the latest 4.2 of MongoDB Community Edition:

  1. From https://fastdl.mongodb.org/win32/mongodb-win32-x86_64-2012plus-4.2.0-signed.msi.sha256, copy the content.
  2. Save the content to a file mongodb-win32-x86_64-2012plus-4.2.0-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-2012plus-4.2.0-signed.msi.sha256 | Out-String).SubString(0,64).ToUpper(); `
$fileHash = (Get-FileHash $Env:HomePath\Downloads\mongodb-win32-x86_64-2012plus-4.2.0-signed.msi).Hash.Trim(); `
echo $sigHash; echo $fileHash; `
$sigHash -eq $fileHash
AF5AF79EFE540DCDDC2825A396C71FCFC4FEB463BC9CADDCCDE20AD126321CCC
AF5AF79EFE540DCDDC2825A396C71FCFC4FEB463BC9CADDCCDE20AD126321CCC
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.