Package Signatures

Overview

This guide covers RabbitMQ release packages signing and how to verify the signatures on downloaded release artifacts.

Release signing allows users to verify that the artifacts they have downloaded were published by a trusted party (such as a team or package distribution service). This can be done using GPG command line tools. Package management tools such as apt and yum also verify repository signatures.

Signing Keys

RabbitMQ release artifacts, both binary and source, are signed using GnuPG and our release signing key.

In addition, the contents of the Debian repositories maintained by Team RabbitMQ are signed using the same key.

Importing Signing Keys

With GPG

Before signatures can be verified, RabbitMQ signing key must be downloaded. The key can be obtained directly or using keys.openpgp.org. The direct download method is recommended because most key servers are prone to overload, abuse and attacks.

Direct Download

The key is distributed via GitHub and rabbitmq.com:

curl -L https://github.com/rabbitmq/signing-keys/releases/download/3.0/rabbitmq-release-signing-key.asc --output rabbitmq-release-signing-key.asc
gpg --import rabbitmq-release-signing-key.asc

Using a Key Server

The key can be imported from keys.openpgp.org:

gpg --keyserver "hkps://keys.openpgp.org" --recv-keys "0x0A9AF2115F4687BD29803A206B73A36E6026DFCA"

Alternative keyservers:

gpg --keyserver "keyserver.ubuntu.com" --recv-keys "0x0A9AF2115F4687BD29803A206B73A36E6026DFCA"

gpg --keyserver "pgp.surfnet.nl" --recv-keys "0x0A9AF2115F4687BD29803A206B73A36E6026DFCA"

gpg --keyserver "pgp.mit.edu" --recv-keys "0x0A9AF2115F4687BD29803A206B73A36E6026DFCA"

With apt

On Debian and Ubuntu systems, assuming that apt repositories are used for installation, trusted repository signing keys must be added to the system before any packages can be installed.

This can be done using key servers or (for the RabbitMQ main signing key) a direct download.

Direct Download

Main RabbitMQ signing key is distributed via GitHub and rabbitmq.com:

curl -1sLf https://github.com/rabbitmq/signing-keys/releases/download/3.0/rabbitmq-release-signing-key.asc | sudo gpg --dearmor > /usr/share/keyrings/com.rabbitmq.team.gpg

Using a Key Server

The same main RabbitMQ signing key can be imported from keys.openpgp.org:

curl -1sLf "https://keys.openpgp.org/vks/v1/by-fingerprint/0A9AF2115F4687BD29803A206B73A36E6026DFCA" | sudo gpg --dearmor > /usr/share/keyrings/com.rabbitmq.team.gpg

When using the Team RabbitMQ modern Erlang PPA, one more key needs to be added:

## Team RabbitMQ's signing key
curl -1sLf "https://keys.openpgp.org/vks/v1/by-fingerprint/0A9AF2115F4687BD29803A206B73A36E6026DFCA" | sudo gpg --dearmor > /usr/share/keyrings/com.rabbitmq.team.gpg

With RPM

On RPM-based systems (RHEL, Fedora, CentOS), assuming that yum repositories are used for installation, rpm --import should be used to import the key.

Direct Download

The key is distributed via GitHub and rabbitmq.com:

rpm --import https://github.com/rabbitmq/signing-keys/releases/download/3.0/rabbitmq-release-signing-key.asc

Verifying Signatures

To check signatures for the packages, download the RabbitMQ signing key and a signature file. Signature files use the .asc extension that follows their artifact filename, e.g. the signature file of rabbitmq-server-generic-unix-4.0.4.tar.xz would be rabbitmq-server-generic-unix-4.0.4.tar.xz.asc.

Then use gpg --verify:

gpg --verify [filename].asc [filename]

Here's an example session, after having retrieved a RabbitMQ source archive and its associated detached signature from the download area:

gpg --verify rabbitmq-server_4.1.2-1_all.deb.asc rabbitmq-server_4.1.2-1_all.deb
# => gpg: Signature made (date elided)
# => gpg:                using RSA key 0A9AF2115F4687BD29803A206B73A36E6026DFCA
# => gpg: Good signature from "RabbitMQ Release Signing Key <info@rabbitmq.com>" [unknown]
# (elided)
# => Primary key fingerprint: 0A9A F211 5F46 87BD 2980  3A20 6B73 A36E 6026 DFCA

If the signature is invalid, a "BAD signature" message will be emitted. If that's the case the origin of the package, the signature file and the signing key should be carefully verified. Packages that fail signature verification must not be used.

If the signature is valid, you should expect a "Good signature" message; if you've not signed our key, you will see a "Good signature" message along with a warning about our key being untrusted.

If you trust the RabbitMQ signing key you avoid the warning output by GnuPG by signing it using your own key (to create your private key run gpg --gen-key):

gpg --sign-key 0x0A9AF2115F4687BD29803A206B73A36E6026DFCA