All of lore.kernel.org
 help / color / mirror / Atom feed
* Updated key for me
@ 2026-10-01 15:05 Mark Brown
  2026-10-13  5:36 ` Uwe Kleine-König
  0 siblings, 1 reply; 4+ messages in thread
From: Mark Brown @ 2026-10-01 15:05 UTC (permalink / raw)
  To: keys


[-- Attachment #1.1: Type: text/plain, Size: 59 bytes --]

Attached as per https://korg.docs.kernel.org/pgpkeys.html.

[-- Attachment #1.2: broonie.asc --]
[-- Type: application/pgp-keys, Size: 325937 bytes --]

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Updated key for me
  2026-10-01 15:05 Updated key for me Mark Brown
@ 2026-10-13  5:36 ` Uwe Kleine-König
  2026-10-13 10:51   ` Mark Brown
  0 siblings, 1 reply; 4+ messages in thread
From: Uwe Kleine-König @ 2026-10-13  5:36 UTC (permalink / raw)
  To: Mark Brown; +Cc: keys

[-- Attachment #1: Type: text/plain, Size: 621 bytes --]

On Thu, Oct 01, 2026 at 04:05:29PM +0100, Mark Brown wrote:
> Attached as per https://korg.docs.kernel.org/pgpkeys.html.

The attachment contains two certificates. A dsa1024 one from 1998 and an
rsa4096 from 2011. I guess only the second was intended? But that also
has (pre-existing) SHA1 issues, according to `sq cert lint`:

Certificate C3F436CA30F5D8EB, key DD6A5FE57B78DB59 uses a SHA-1-protected binding signature.

Would be great if you fixed that. If you don't know how, I'm glad to
help.

Other than that, there are a few new signatures for C3F436CA30F5D8EB, a
revoked UID and two new subkeys.

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Updated key for me
  2026-10-13  5:36 ` Uwe Kleine-König
@ 2026-10-13 10:51   ` Mark Brown
  2026-10-13 11:19     ` Uwe Kleine-König
  0 siblings, 1 reply; 4+ messages in thread
From: Mark Brown @ 2026-10-13 10:51 UTC (permalink / raw)
  To: Uwe Kleine-König; +Cc: keys

[-- Attachment #1: Type: text/plain, Size: 723 bytes --]

On Tue, Oct 13, 2026 at 07:36:58AM +0200, Uwe Kleine-König wrote:
> On Thu, Oct 01, 2026 at 04:05:29PM +0100, Mark Brown wrote:
> > Attached as per https://korg.docs.kernel.org/pgpkeys.html.

> The attachment contains two certificates. A dsa1024 one from 1998 and an
> rsa4096 from 2011. I guess only the second was intended? But that also

I mean, I just exported all my keys - I don't really mind.

> has (pre-existing) SHA1 issues, according to `sq cert lint`:

> Certificate C3F436CA30F5D8EB, key DD6A5FE57B78DB59 uses a SHA-1-protected binding signature.

> Would be great if you fixed that. If you don't know how, I'm glad to
> help.

That message does not even tell me enough to identify a problem.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Updated key for me
  2026-10-13 10:51   ` Mark Brown
@ 2026-10-13 11:19     ` Uwe Kleine-König
  0 siblings, 0 replies; 4+ messages in thread
From: Uwe Kleine-König @ 2026-10-13 11:19 UTC (permalink / raw)
  To: Mark Brown; +Cc: keys

[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]

Hello Mark,

On Tue, Oct 13, 2026 at 11:51:12AM +0100, Mark Brown wrote:
> On Tue, Oct 13, 2026 at 07:36:58AM +0200, Uwe Kleine-König wrote:
> > On Thu, Oct 01, 2026 at 04:05:29PM +0100, Mark Brown wrote:
> > > Attached as per https://korg.docs.kernel.org/pgpkeys.html.
> > 
> > The attachment contains two certificates. A dsa1024 one from 1998 and an
> > rsa4096 from 2011. I guess only the second was intended? But that also
> > has (pre-existing) SHA1 issues, according to `sq cert lint`:
> >
> > Certificate C3F436CA30F5D8EB, key DD6A5FE57B78DB59 uses a SHA-1-protected binding signature.
> >
> > Would be great if you fixed that. If you don't know how, I'm glad to
> > help.
> 
> That message does not even tell me enough to identify a problem.

It means that the proof that the encryption subkey DD6A5FE57B78DB59
belongs to your primary key is based on SHA1 instead of something that
is still considered safe for some time.

The easy fix is

	sq cert lint --fix --output - --cert DD6A5FE57B78DB59 | gpg --import

(if sq can access your primary key) or (I guess) Konstantin's
rebind-modern-hash.py script (can be found in
git@gitolite.kernel.org:/pub/scm/docs/kernel/pgpkeys.git).
Or if you want to go through the deep details with GnuPG, see
https://lore.kernel.org/keys/fxotnlhsyl2frp54xtguy7ryrucuwselanazixeax3motyyoo3@7vf7ip6gxyvx/
.

Best regards
Uwe



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2026-10-13 11:19 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-10-01 15:05 Updated key for me Mark Brown
2026-10-13  5:36 ` Uwe Kleine-König
2026-10-13 10:51   ` Mark Brown
2026-10-13 11:19     ` Uwe Kleine-König

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.