All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Inki Dae <inki.dae@samsung.com>,
	keys@kernel.org,  Inki Dae <daeinki@gmail.com>,
	Chanwoo Choi <cwchoi00@gmail.com>
Subject: Re: Updated PGP key 0C4312B8 (daeinki)
Date: Thu, 29 Oct 2026 15:35:27 +0100	[thread overview]
Message-ID: <auNZM-X4fsR25aT7@monoceros> (raw)
In-Reply-To: <15516f6e-d1af-4be1-8c24-8ae07e6e1101@kernel.org>

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

On Thu, Oct 29, 2026 at 10:41:40AM +0100, Krzysztof Kozlowski wrote:
> On 29/10/2026 09:54, Uwe Kleine-König wrote:
> > Hello Inki,
> > 
> > On Thu, Oct 29, 2026 at 03:37:26PM +0900, Inki Dae wrote:
> >> I have extended the expiration of my PGP key
> >> 3512 8EA0 5ECD 85D3 C6A6 C727 5738 3489 0C43 12B8 (kernel.org account: daeinki).
> >> The updated public key is below.
> >>
> >> -----BEGIN PGP PUBLIC KEY BLOCK-----
> >>
> >> mQINBFByVSABEAC3YtraHYqLMBl7qG48vfX9K69OTp7aPpoThy1kzkYc89r+dFHY
> >> oJF/hJqzyVGeKgxaIlkpV2NTPeXvITZwDePfNlt4rrTgUtil22dFa6R6rX8UmUXp
> >> [...]
> >> vSaRm79eeDAhGPPkvBxwDf8Xz2x/AhnS9q8Ifwot+Yx+U966dx3ZR4jPhNmB35DW
> >> T2f3xOgbI20WBkIWFa2QDDERcGqcNfm3OFadwpN4rGXYuBOJIRjMO40S3QrUFsuI
> >> D3OLjvuZrrMH6BF4oA8MuqyJWeNUpA==
> >> =MXVC
> >> -----END PGP PUBLIC KEY BLOCK-----
> > 
> > That certficate (573834890C4312B8) isn't in the keyring yet, and it's
> > not well enough connected to be added. The issue is that there are
> > signatures by Chanwoo Choi (9CCDDF2CDEEBCF53) and Krzysztof Kozlowski
> > (1B93437D3B41629B), but they are bound using SHA1 and so are not
> > considered for additions to the keyring. (I added them to Cc: in case
> > they want to resign your certificate.)

I looked at an older revision of the keyring, in the meantime Konstantin
restored the keys that were removed earlier in a separate directory. So
my statement wasn't correct, and an update works fine.

> I did re-sign all my signatures as part of "resigned keys" effort, so
> from my part this should not be a problem... but that might be after
> your commit 2dd67ee0231ccc4ee53cb3d1fde10b122de1bd18 removing the
> expired keys, so maybe I did not re-signed that one?

Yes, I guess so.
 
> Considering Linus' position on expiration date, maybe we should not drop
> them?

As written above, that is already a solved problem now.

Best regards
Uwe

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

      reply	other threads:[~2026-10-29 14:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20261029063727epcas1p442a22eaf19cb80864ca4f973f98ca404@epcas1p4.samsung.com>
2026-10-29  6:37 ` Updated PGP key 0C4312B8 (daeinki) Inki Dae
2026-10-29  8:54   ` Uwe Kleine-König
2026-10-29  9:41     ` Krzysztof Kozlowski
2026-10-29 14:35       ` Uwe Kleine-König [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=auNZM-X4fsR25aT7@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=cwchoi00@gmail.com \
    --cc=daeinki@gmail.com \
    --cc=inki.dae@samsung.com \
    --cc=keys@kernel.org \
    --cc=krzk@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.