PGP keysigning at LPC/OSSE 2026 (Reminder for registration)

PGP keysigning at LPC/OSSE 2026 (Reminder for registration)

[Uwe Kleine-König]

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

Hello,

this is a reminder for the PGP keysigning event held during Linux
Plumbers and Open Source Summit Europe in Prague this October.

While it's not mandatory, it will speed up and simplify the processes if
you register with your certificate for the event. Please do so by
sending your public key to lpcosse-keysigning@baylibre.com until
2026-09-27 08:00 UTC. If you saw the initial announcement[1] and thought
it was still to early and I'm on vacation, please hit reply now and
attach (or include inline) your certificate which can probably be
generated using:

	gpg --export --armor your-email-address@example.com

.

I will create a list of all registrants and their certificates such that
you will end up with less small paper strips to handle. It will also
help me to estimate the size of the group such that an appropriate place
for the meeting can be selected.

Note the list of participants will be public. It contains essentially
the info from your certificate. If you have concerns about that, please
don't register. (But note that if you're using your key in the
community, the same information is out there anyhow.)

As long as my time permits, I will also look at the certificates I
receive and point out things that might be worth doing before the event.
So in your own interest don't wait until a few seconds before the
registration deadline. Also if I don't reply that's a strong hint that
Google didn't accept your mail. Sending your mail early allows to catch
that.

If things are unclear, don't hesitate to ask. I created
#lpcosse2026-keysigning on the libera irc network for that, or send me
an email to the above email alias.

Looking forward to meet you in Prague,
Uwe

[1] https://lore.kernel.org/lkml/lpcosse2026-keysigning@baylibre.com

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

Re: PGP keysigning at LPC/OSSE 2026 (Reminder for registration)

[Geert Uytterhoeven]

Hi Uwe,

On Tue, 15 Sept 2026 at 10:25, Uwe Kleine-König <ukleinek@kernel.org> wrote:
> this is a reminder for the PGP keysigning event held during Linux
> Plumbers and Open Source Summit Europe in Prague this October.

Thanks for organizing!

> While it's not mandatory, it will speed up and simplify the processes if
> you register with your certificate for the event. Please do so by
> sending your public key to lpcosse-keysigning@baylibre.com until
> 2026-09-27 08:00 UTC. If you saw the initial announcement[1] and thought
> it was still to early and I'm on vacation, please hit reply now and
> attach (or include inline) your certificate which can probably be
> generated using:
>
>         gpg --export --armor your-email-address@example.com

Note that this would include all your expired/revokes keys (if any),
so you may want to specify the key ID instead.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Re: PGP keysigning at LPC/OSSE 2026 (Reminder for registration)

[Uwe Kleine-König]

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

Hello Geert,

On Sun, Sep 20, 2026 at 10:35:36AM +0200, Geert Uytterhoeven wrote:
> On Tue, 15 Sept 2026 at 10:25, Uwe Kleine-König <ukleinek@kernel.org> wrote:
> > this is a reminder for the PGP keysigning event held during Linux
> > Plumbers and Open Source Summit Europe in Prague this October.
> 
> Thanks for organizing!
> 
> > While it's not mandatory, it will speed up and simplify the processes if
> > you register with your certificate for the event. Please do so by
> > sending your public key to lpcosse-keysigning@baylibre.com until
> > 2026-09-27 08:00 UTC. If you saw the initial announcement[1] and thought
> > it was still to early and I'm on vacation, please hit reply now and
> > attach (or include inline) your certificate which can probably be
> > generated using:
> >
> >         gpg --export --armor your-email-address@example.com
> 
> Note that this would include all your expired/revokes keys (if any),
> so you may want to specify the key ID instead.

That's right, and that's why I wrote "probably" above. So if you're
unsure, check the output of

	gpg --list-key $whatever

to match what you intend to send and only then do

	gpg --export --armor $whatever

.

Best regards
Uwe

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