Re: Many more sigs show when I add --with-colons to --list-sigs

--===============8953205463203893685==
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="ZolE3xjmf13f+EOv"
Content-Disposition: inline


--ZolE3xjmf13f+EOv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 29, 2026 at 10:47:09AM -0400, Robert J. Hansen via Gnupg-users =
wrote:
> > Thanks. I guess this helps explain why some of the signatures listed
> > by --check-sigs as usable were dsa1024, while others were unusable. My
> > dsa1024 signature is listed as usable on other people's keys, so I
> > guess that means my key doesn't use SHA-1?
>=20
> Your certificate doesn't have a single RIPEMD160 signature on it.
>=20
> Let's look at the machine-readable signature line:
>=20
> sig:?::17:DBC3EBFC33E3FE56:995424332::::[User ID not found]:10x:::::2:
>=20
> That next-to-final field, the '2', represents the hash algorithm used in
> the signature. 2 corresponds to SHA-1. RIPEMD160 corresponds to 3.
>=20
> You don't have a single signature line with a 3 in that field.

I've got some 10's later on with my self-signatures for my newer
rsa4096 keys.

Maybe I'm confused by the output of --check-sigs. Since most of the
keys have a "!" and a few have "%", and since % represents a
non-supported algorithm, I was thinking that the % rows must have been
the SHA-1 sigs and the ! rows were OK.

If in fact the vast majority of signatures on my key are invalid
because of SHA-1, and most of my signatures are also invalid, I'm
wondering if it might make sense to start fresh with a new key that
doesn't have all that potentially confusing old baggage.

Walt

--ZolE3xjmf13f+EOv
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEsBVFaKgbhBVkCl7wWw6znYG+qIkFAmpqIREACgkQWw6znYG+
qIk/BxAAlEE8egfrBbn7wMRmJw8Qq5U0UMLQsAoSFL/X9v4R8yVpcBmeL6LQt2D8
Lqz6/RpFDFP9YXpix8rLFWIC6UNwJAYlPCaTb8Rb8iYbnzu5jkUzDJvFJVbEnOLx
8jL3AODMFToA2MZYai9tkBf8xMQ2WDtHktbX53djDUYmRidrLkXlVlSJW3qab7oQ
9cwTKGBDD0Nhk5g6Vl4/8bWn5/u6vQ100jh/FEq+zS+YAl2ZhoIUBobv6TsPJFp0
TArwhdHUnCNyoTvuIqFoddhqQfWgGVnEGnkD2w42G53Z989oAGo8Uepjcz5gLz5N
DGyq7DTZznOhpuq0iKuFiJUIBCxn7dmxXpXVl24Hh5EIhd1oimw6qxLV9hV0betQ
IawrwbtC1/HKJARdn4QxiI+5cDSin8gzIX5hwnqMPOfchcVDe1Pzik3O+4L5Yi4P
jXXO7lasNBN/esHugKqZN7J5C4E/JGcV43mHo1+N829DTooM6tNzuaFVePt9nd5j
zgNestNM8l0enoAJ6L6tBpNvtbRQQR/mlMy2Zl4Dw57fH+vELLo/30higtaMpCDB
6x0R8RZlW7F6/UpVko9l5vDV8tg9zMyay8tbXYq+GJuJ6SxYYmJLxI0Fkmz3O7pu
j8Kl6YEs9pWbiKZ6W5o4qmK0yNPmey1y4RC65Y4XSCcIWPi7nSY=
=5lGr
-----END PGP SIGNATURE-----

--ZolE3xjmf13f+EOv--


--===============8953205463203893685==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gnupg-users mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-users

--===============8953205463203893685==--