You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docs reference a GPG key (2359E6538C0613E652955E6C188EDD3B7B22E6A3) as the SecureDrop Release key, but when using it to verify the authenticity and integrity of the securedrop-workstation-dom0-config package, the expected output references a different key, which ID ends in 00f4ad77.
securedrop-workstation-dom0-config-<versionNumber>-1.fc25.noarch.rpm:
Header V4 RSA/SHA256 Signature, key ID 00f4ad77: OK
Header SHA1 digest: OK
V4 RSA/SHA256 Signature, key ID 00f4ad77: OK
MD5 digest: OK
Expected
Since the package verification output MUST match the documentation before the reader proceeds with the installation, the documentation should reference the 7b22e6a3 key consistently.
Currently
The docs reference a GPG key (
2359E6538C0613E652955E6C188EDD3B7B22E6A3
) as the SecureDrop Release key, but when using it to verify the authenticity and integrity of the securedrop-workstation-dom0-config package, the expected output references a different key, which ID ends in00f4ad77
.Expected
Since the package verification output MUST match the documentation before the reader proceeds with the installation, the documentation should reference the
7b22e6a3
key consistently.Context
The SecureDrop release key was recently updated, and the most recent key is indeed
7b22e6a3
.See freedomofpress/securedrop-workstation#700
The text was updated successfully, but these errors were encountered: