Bug 2516938 - gpg-sq throws "Unsupported hash algorithm: RipeMD160"
Summary: gpg-sq throws "Unsupported hash algorithm: RipeMD160"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rust-sequoia-chameleon-gnupg
Version: 44
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Fabio Valentini
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-15 07:47 UTC by Phil
Modified: 2026-10-03 01:35 UTC (History)
2 users (show)

Fixed In Version: rust-sequoia-chameleon-gnupg-0.13.1-19.fc46 rust-sequoia-chameleon-gnupg-0.13.1-19.fc45 rust-sequoia-chameleon-gnupg-0.13.1-19.fc44 rust-sequoia-chameleon-gnupg-0.13.1-19.fc43
Clone Of:
Environment:
Last Closed: 2026-09-24 07:58:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Phil 2026-08-15 07:47:28 UTC
"gpg-sq -k" throws "Unsupported hash algorithm: RipeMD160" instead of showing the keyring contents.

Reproduced on different Fedora 44 machines.

Reproducible: Always

Steps to Reproduce:
1. rm -rf /tmp/gnupg-test/ ; mkdir -m 0700 /tmp/gnupg-test ; export GNUPGHOME=/tmp/gnupg-test
2. gpg --full-generate-key
3. gpg-sq -k
Actual Results:
/tmp/gnupg-test/pubring.cert.d
------------------------------
pub   ed25519 2026-08-15 [SC]
      F80227DACE1CF366AA79E05A5E72FC634E477B2A
gpg: Unsupported hash algorithm: RipeMD160

Expected Results:
gpg: checking the trustdb
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
/tmp/gnupg-test/pubring.kbx
---------------------------
pub   ed25519 2026-08-15 [SC]
      F80227DACE1CF366AA79E05A5E72FC634E477B2A
uid           [ultimate] Test Key <testkey@localhost>
sub   cv25519 2026-08-15 [E]

Additional Information:
happens with DEFAULT and LEGACY crypto policy.

Comment 1 Fabio Valentini 2026-08-15 13:37:57 UTC
This is a known regression from switching to the "ossl" bindings for OpenSSL,
which do not support RipeMD160 in their latest version.

See also release notes for sequoia-openpgp v2.4.0:
https://gitlab.com/sequoia-pgp/sequoia/-/blob/main/openpgp/NEWS

Since I considered this a functional regression in sequoia-openpgp v2.4.0,
I filed an issue against the "ossl" bindings to add RipeMD160 support:
https://github.com/latchset/kryoptic/issues/477

The next release of "ossl" should have the necessary wrappers so sequoia-openpgp can re-enable RipeMD160 support with the OpenSSL backend.

Comment 2 Fedora Update System 2026-09-24 07:55:26 UTC
FEDORA-2026-dee864703a (rust-ossl-1.5.3-1.fc46, rust-sequoia-cert-store-0.7.6-1.fc46, and 4 more) has been submitted as an update to Fedora 46.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-dee864703a

Comment 3 Fedora Update System 2026-09-24 07:56:16 UTC
FEDORA-2026-bcdaa5631c (rust-ossl-1.5.3-1.fc45, rust-sequoia-cert-store-0.7.6-1.fc45, and 4 more) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-bcdaa5631c

Comment 4 Fedora Update System 2026-09-24 07:56:37 UTC
FEDORA-2026-b3677a03d6 (rust-ossl-1.5.3-1.fc44, rust-sequoia-cert-store-0.7.6-1.fc44, and 4 more) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-b3677a03d6

Comment 5 Fedora Update System 2026-09-24 07:57:23 UTC
FEDORA-2026-b2a38cf3a3 (rust-ossl-1.5.3-1.fc43, rust-sequoia-cert-store-0.7.6-1.fc43, and 4 more) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-b2a38cf3a3

Comment 6 Fedora Update System 2026-09-24 07:58:36 UTC
FEDORA-2026-dee864703a (rust-ossl-1.5.3-1.fc46, rust-sequoia-cert-store-0.7.6-1.fc46, and 4 more) has been pushed to the Fedora 46 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2026-09-25 01:34:55 UTC
FEDORA-2026-b3677a03d6 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-b3677a03d6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-b3677a03d6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2026-09-25 01:55:38 UTC
FEDORA-2026-b2a38cf3a3 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-b2a38cf3a3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-b2a38cf3a3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2026-09-25 02:15:43 UTC
FEDORA-2026-bcdaa5631c has been pushed to the Fedora 45 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-bcdaa5631c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-bcdaa5631c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2026-10-03 00:22:08 UTC
FEDORA-2026-bcdaa5631c (rust-ossl-1.5.3-1.fc45, rust-sequoia-cert-store-0.7.6-1.fc45, and 4 more) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2026-10-03 01:11:20 UTC
FEDORA-2026-b3677a03d6 (rust-ossl-1.5.3-1.fc44, rust-sequoia-cert-store-0.7.6-1.fc44, and 4 more) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2026-10-03 01:35:13 UTC
FEDORA-2026-b2a38cf3a3 (rust-ossl-1.5.3-1.fc43, rust-sequoia-cert-store-0.7.6-1.fc43, and 4 more) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.