Re: [email protected]

On 9/24/25 03:35, Uwe Kleine-König wrote:
> Hello Joseph,
>
> On Tue, Sep 23, 2025 at 01:19:52PM -0400, Joseph Salisbury wrote:
>> -----BEGIN PGP PUBLIC KEY BLOCK-----
>>
>> mQINBE8KtKMBEADJ3sa+47aMnk7RF/fn4a7IvRDV19Z1L2Qq1c6dxcvtXP9Mq0i9
>> 5hBgPnNB2FFJJ4QvJUJ6hYaniqgX3VkvKvjOcOwKz78NYF0HuIZqTTwd2qWpECXq
>> ...
>> -----END PGP PUBLIC KEY BLOCK-----
> Your key is using SHA-1 in two places:
>
> 	$ sq cert lint < /tmp/yourcert
> 	Certificate 6CEF3D27CA5B141E contains a User ID (Joseph Salisbury <[email protected]>) protected by SHA-1
> 	Certificate 6CEF3D27CA5B141E, key 87AC77B3BF827F80 uses a SHA-1-protected binding signature.
> 	...
>
> It would be great if you could fix those. Practical breakage is not
> known yet, but still I recommend to update your key to a safer hash
> algorithm to reduce attacking surface.
>
> Find more details at
> https://lore.kernel.org/keys/fxotnlhsyl2frp54xtguy7ryrucuwselanazixeax3motyyoo3@7vf7ip6gxyvx/T/#u
> which also describes a procedure to (hopefully) fix your key and if
> questions arise don't hesitate to ask.
>
> Best regards
> Uwe
Thanks for the heads up, Uwe!

I fixed those and sent an updated key to the list.

Thanks again,

Joe