#1102685 gpg-sq: does not print algorithm number with -v --version

Package:
gpg-sq
Source:
gpg-sq
Description:
gpg-like OpenPGP CLI toolkit
Submitter:
brian m. carlson
Date:
2025-04-28 17:36:04 UTC
Severity:
normal
Tags:
#1102685#5
Date:
2025-04-11 21:46:19 UTC
From:
To:
When using the `-v` flag with `--version`, GnuPG prints algorithm
numbers which can be used to configure preferences:

Home: /home/bmc/.gnupg
Supported algorithms:
Pubkey: RSA (1), ELG (16), DSA (17), ECDH (18), ECDSA (19), EDDSA (22)
Cipher: IDEA (S1), 3DES (S2), CAST5 (S3), BLOWFISH (S4), AES (S7),
        AES192 (S8), AES256 (S9), TWOFISH (S10), CAMELLIA128 (S11),
        CAMELLIA192 (S12), CAMELLIA256 (S13)
Hash: SHA1 (H2), RIPEMD160 (H3), SHA256 (H8), SHA384 (H9), SHA512 (H10),
      SHA224 (H11)
Compression: Uncompressed (Z0), ZIP (Z1), ZLIB (Z2), BZIP2 (Z3)
----

However, gpg-sq does not:
----
% gpg-sq -v --version
gpg (GnuPG-compatible Sequoia Chameleon) 2.2.40
Sequoia gpg Chameleon 0.13.1
sequoia-openpgp 2.0.0
Copyright (C) 2024 Sequoia PGP
License GNU GPL-3.0-or-later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/bmc/.gnupg
Supported algorithms:
Pubkey: RSA, DSA, ECDH, ECDSA, EDDSA, X25519, X448, Ed25519,
        Ed448
Cipher: BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128,
        CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224, SHA3-256,
      SHA3-512
Compression: Uncompressed, ZIP, ZLIB, BZIP2
----

This makes it harder to set preferences in an unambiguous way or to
interpret the output of `gpg --list-packets`.  For instance, while I
have memorized the fact that SHA512 is algorithm 10, I don't know what
algorithm 14 is, so without this functionality I have to go look at the
RFC, which is less convenient and requires that I be online.

#1102685#10
Date:
2025-04-12 09:14:05 UTC
From:
To:
control: forwarded -1 https://gitlab.com/sequoia-pgp/sequoia-chameleon-gnupg/-/issues/130
thanks

Hi Brian,
[...]
[...]

thank you for reporting this bug, I've forwarded it upstream.