Re: Many more sigs show when I add --with-colons to --list-sigs
Walt Mankowski via Gnupg-users <[email protected]> Wed, 29 Jul 2026 20:59:04 -0400
| Newsgroups | gmane.comp.encryption.gpg.user |
|---|---|
| Message-ID | <[email protected]> |
--===============1537072096300290771== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="SS2oGh064ENtKnAu" Content-Disposition: inline --SS2oGh064ENtKnAu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 29, 2026 at 12:44:26PM -0400, Robert J. Hansen via Gnupg-users = wrote: > > I've got some 10's later on with my self-signatures for my newer > > rsa4096 keys. >=20 > Unless you're looking to write a GnuPG output parser, I suggest not even > looking at the machine-readable output. There's nothing useful to you the= re. Except for proof that the signatures were in fact made with SHA-1. Look, I'm just trying to understand what's going on. It's not exactly straightforward. > The best time to migrate away from DSA keys was in the year 2000, when > the RSA patent was relinquished. The second best time is now. >=20 > Seriously: I don't mean to be a jerk, but you're 26 years late to the par= ty. Seriously, I don't mean to be a jerk either, but this also means that gpg has had 26 years to make the output be more consistent and easier to understand. Why do --list-sigs and --check-sigs show different signatures? Why is --check-sigs saying that some of my signatures are usable if they were made with SHA-1? What does "usable" even mean in this context? --SS2oGh064ENtKnAu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEsBVFaKgbhBVkCl7wWw6znYG+qIkFAmpqodgACgkQWw6znYG+ qIkJyhAAnpQa9jd8tepomgt8gPMTZI9SkhWJcqaTDT8D2Q5epNgJJ+zCemDJlTfM la/MC5pQZFwZsxDfpu6rM3L3dsWyKmBKYUfflrWhdItRr83BdCf05/bD0g171+QV w3YmtfEQmnGZuh4cwiH3YFvLYEc/MQaZ3qQmusElUF7p+Xy2WZNeWLeilPdFrtuD bAr35M0EsThCOH0gUuunhrzHGfwAFVuWgtyr5wpgrDCckhgM0ZmU72ERv9fbMqCH y4GgTt9ZDp7MOdWB1+iWeLFNFOM7szA8GzHPnDTKu/VlpckpKSqkL4ERtXOxWADR /8MFsBf1Uohw5uCgIpzjKe+H3va9LIW0d79c1wVJiZmlg1lrIyyDbZKScHxeMyKU Suqm+j+STDhEF+hw7pnzGN6GKDq/5Dej2masL0cSw6C4+oJTjFS29Rlhovb9AwKK WzNITKJDWy5yvlfk4cuaPy9d1Iz9Sd9/fPNTmEcwtfqfryxtC4BSrbazPsSQhtNo 2OcLEKbfSEfJH9YHuURd5WyX1H+YWW4YZUkuXCO3CitFZQNxTxfNacfxfzO2IqoY JeDSADZmxNjZeQhZXeROr4053vl5XetIneVmjsqUR/SMH8M44wH2so04V/8aeIKf 1JZhUXifA/ec3jsEkwtGAP92h3ESDuJvO02f01i0VKpBMafdn8k= =CFfL -----END PGP SIGNATURE----- --SS2oGh064ENtKnAu-- --===============1537072096300290771== 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 --===============1537072096300290771==--