- Task
- Version · 6.0.2
- Create
Verify a Liquibase Secure server download
Last updated: November 17, 2026
Check that the liquibase-platform CLI archive you downloaded came from Liquibase before you run it. This check is optional. It is for teams whose security policy requires checking a download before it runs. A GPG signature proves the release's checksum file came from Liquibase, and the checksum file proves the archive matches what Liquibase published.
Before you begin
You must have downloaded the
liquibase-platformCLI archive for your platform, as in step 1 of Install Liquibase Secure server, and not yet extracted it.You must have
gpgandcurlon the machine that holds the archive. On Windows, run every command in this article in the same WSL2 Linux shell you downloaded the archive in.
Procedure
Download the checksum files
The download page holds a SHA256SUMS file that covers every archive, and SHA256SUMS.asc, a GPG signature over SHA256SUMS. Download both into the folder that holds the archive:
Check the signature
First check that SHA256SUMS comes from Liquibase. It is signed with the same key as Liquibase Secure. Import the Liquibase public key and check the signature:
gpg must report Good signature from "Liquibase <devops@liquibase.com>" and the primary key fingerprint A33B A2DD 58AB DFC5 441F 425F 0826 3CBA 8BCD 9EE8. A warning that the key is not certified with a trusted signature only means you have not signed the key yourself. If gpg reports BAD signature, or any other fingerprint, SHA256SUMS did not come from Liquibase. Stop there, and do not run the archive.
Check the archive's checksum
Then check the archive against SHA256SUMS. Open the tab for your operating system and run its command:
The command prints the archive's file name followed by OK. Any other result means the archive is not the one Liquibase published. Download it again, and do not run it.
When the archive passes, go back to step 1 of Install Liquibase Secure server to extract it.