Re: Keys using SHA-1 in the kernel keyring
Konstantin Ryabitsev <[email protected]> Fri, 21 Mar 2025 15:20:44 -0400
| Newsgroups | org.kernel.linux.keys |
|---|---|
| Message-ID | <20250321-cordial-panther-of-chemistry-0e46ad@lemur> |
On Fri, Feb 07, 2025 at 06:09:40PM +0100, Uwe Kleine-König wrote: > Given that fixing is so easy and SHA-1 is broken since 20 years, at > least getting the high profile users who regularly sign archives (or > keyring commits :-) looks beneficial to me. My general concern about this is two-fold: 1. What is the actual attack scenario where this could be abused? I know you pointed out that Linus and Greg have sha1 certificates, but they are either on UIDs or on their E subkeys, which they don't use for signing. Both of them have [SC] keys, so I don't believe the following case wouldn't really apply: > (You could even argue that the old archives should get resigned, but I'd > already be happy if future signatures will be fixed.) Since they aren't signed by subkeys but by main [SC] keys, I don't believe anything would be gained by resigning the old archives. 2. The second concern is the fact that we're changing keys for Linus and Greg, and just the fact that their keys will have obscure changes may create a negative impact of its own from the social engineering perspective. If someone sees that Linus's key has changed, but after they pull in the update there is no visible change to the key in the keyring is going to cause confusion. 3. Third concern is more of an aside that Linus hates PGP and getting him to do anything with his keys is usually an endeavour. :) -K