What to check first
Get the publisher’s public key from your release policy. Verify the signature on the exact archive before comparing its SHA-256 with the approval.
KeySigner setups
- Verify an RSA signature and compare the archive with the release approval →KeySigner release history and OpenSSL
KeySigner setup requirements →
Provider walkthroughs
What it covers
The release check covers the archive digest. Publisher keys and OpenSSL certificate trust remain under your own policy.
Troubleshooting
Does OpenSSL verify the signature while KeySigner reports a different digest?
Compare the SHA-256 of the exact file OpenSSL verified with the approved digest. Ask the release owner whether the archive was built again after approval.
Check an approved npm archive with OpenSSL or GnuPG →
For a connection failure, ask the endpoint operator to check the service and certificate chain. For a local verification failure, check the input files and trust configuration.
Documentation and support
OpenSSL documentation
Review certificate verification and trust options
Verify detached signatures with OpenSSL