On Mon, Sep 05, 2022 at 05:44:26PM +0300, Laurent Pinchart wrote: > On Mon, Sep 05, 2022 at 01:41:11PM +0000, Sakari Ailus wrote: > > On Tue, Aug 23, 2022 at 12:53:44PM +0200, Hans Verkuil wrote: > > > 16:45-18:00 Anything else? > > > > I think it'd be great to have a GPG key signing party at the end of the > > meeting. > > It's a good idea. Could everybody please send their GPG key fingerprint > in an e-mail reply to prepare for that ? It can easily be retrieved with > 'gpg -K' (make sure to pick the right key if you have multiple of them). > I'll start: > > sec rsa4096/0xF045C2B96991256E 2014-10-09 [C] > 94231B980100EC619AC10E10F045C2B96991256E > uid [ultimate] Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> > > If you're generating a key for the occasion, create a primary key with > the Certify (C) capability only, and create separate sub-keys for > Signature (S) and Encryption (E). There's little reason these days to > use less than 4096 bits for the primary key if you opt for RSA. The > subkeys should have an expiration date. > > The primary key can then be moved to safe storage, you will only need > the subkeys for daily usage. The primary key will be used only to > create new subkeys and to sign other people's keys. sec# ed25519 2018-09-15 [C] [expires: 2023-03-17] BE5675C37E818C8B5764241C254BCFC56BF6CE8D uid [ultimate] Maxime Ripard <maxime.ripard@xxxxxxxxxxx> uid [ultimate] Maxime Ripard <mripard@xxxxxxxxxx> uid [ultimate] Maxime Ripard (Work Address) <maxime@xxxxxxxxxx> ssb> cv25519 2018-09-15 [E] [expires: 2023-03-17] ssb> ed25519 2018-09-15 [S] [expires: 2023-03-17] ssb> ed25519 2018-09-15 [A] [expires: 2023-03-17] Thanks! Maxime
Attachment:
signature.asc
Description: PGP signature