Skip to contentSkip to conversation

Replacement GPG key for Sasha Levin

DISCUSSION Sasha Levin 3 participants 4 messages Mar 25 – Mar 26

lore
Share & tools
lore
#0 lore raw

Hi folks,

Please add my new ed25519 GPG key to the keyring, replacing my old RSA-4096 key (E27E5D8A3403A2EF66873BBCDEA66FF797772CDC). The new key is cross-signed by the old one.

Signature · 2 lines
Thanks,
Sasha
#1 lore raw

Hello Sasha,

Quoted 2 lines · Sasha Levin

Please add my new ed25519 GPG key to the keyring, replacing my old RSA-4096 key (E27E5D8A3403A2EF66873BBCDEA66FF797772CDC).

In contrast to the old certificate the new one makes sq cert lint
happy, so that's a good step. (The old one resulted in
Certificate DEA66FF797772CDC contains a User ID (Sasha Levin <[email protected]>) protected by SHA-1 Certificate DEA66FF797772CDC contains a User ID (Sasha Levin <[email protected]>) protected by SHA-1 Certificate DEA66FF797772CDC, key D0065D755EB09DBB uses a SHA-1-protected binding signature.
.)

Quoted 1 line

The new key is cross-signed by the old one.

The old cert only has a single trust path (see
https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git/plain/graphs/DEA66FF797772CDC.svg),
as the new cert is only signed by the old, it also only has a single path through the old one. It would be great to improve that, still because that single path goes away when the old cert is removed.

Best regards
Uwe

#2 lore raw
Quoted 13 lines · Uwe Kleine-König

Hello Sasha,

Quoted 2 lines · Sasha Levin

Please add my new ed25519 GPG key to the keyring, replacing my old RSA-4096 key (E27E5D8A3403A2EF66873BBCDEA66FF797772CDC).

In contrast to the old certificate the new one makes sq cert lint
happy, so that's a good step. (The old one resulted in
Certificate DEA66FF797772CDC contains a User ID (Sasha Levin <[email protected]>) protected by SHA-1 Certificate DEA66FF797772CDC contains a User ID (Sasha Levin <[email protected]>) protected by SHA-1 Certificate DEA66FF797772CDC, key D0065D755EB09DBB uses a SHA-1-protected binding signature.
.)

Quoted 7 lines
Quoted 1 line

The new key is cross-signed by the old one.

The old cert only has a single trust path (see
https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git/plain/graphs/DEA66FF797772CDC.svg),
as the new cert is only signed by the old, it also only has a single path through the old one. It would be great to improve that, still because that single path goes away when the old cert is removed.

Ugh... I thought I had a few more signatures there.

Thanks for pointing it out. Looks like I need to ask a few folks for signatures during LPC/LSF :)

Signature · 2 lines
Thanks,
Sasha
#3 lore raw
In reply to Sasha Levin
Quoted 5 lines · Sasha Levin

Hi folks,

Please add my new ed25519 GPG key to the keyring, replacing my old RSA-4096 key (E27E5D8A3403A2EF66873BBCDEA66FF797772CDC). The new key is cross-signed by the old one.

Added.

Thanks,

Signature · 1 line
KR