Hi Hans, On Wed, Sep 07, 2022 at 08:51:48AM +0200, Hans Verkuil wrote: > Hi Laurent, > > On 05/09/2022 16:44, 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. > > > > Can you also give instructions on what to do at the key signing party? > > I do this so rarely that I always forget what magic gpg commands I need > to make to sign keys. > > If everyone has this information at hand, then we can quickly proceed with > this on Monday. There's one here (directly linking to the signing section albeit the rest is important, too): <URL:https://www.cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html#id2557964> I also wrote a small script that assumes there will be no errors of any sort at any point of time, in conjunction with the e-mail on the key list. -- Sakari Ailus
