public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: "Hans Verkuil" <hverkuil@xs4all.nl>,
	linux-media@vger.kernel.org,
	"Kieran Bingham" <kieran.bingham@ideasonboard.com>,
	"Nicolas Dufresne" <nicolas@ndufresne.ca>,
	"Benjamin Gaignard" <benjamin.gaignard@collabora.com>,
	"Hidenori Kobayashi" <hidenorik@chromium.org>,
	"Paul Kocialkowski" <paul.kocialkowski@bootlin.com>,
	"Jacopo Mondi" <jacopo@jmondi.org>,
	"Ricardo Ribalda" <ribalda@chromium.org>,
	"Maxime Ripard" <maxime@cerno.tech>,
	"Daniel Scally" <djrscally@gmail.com>,
	"Jernej Škrabec" <jernej.skrabec@gmail.com>,
	"Dave Stevenson" <dave.stevenson@raspberrypi.com>,
	"Philipp Zabel" <p.zabel@pengutronix.de>
Subject: Re: [ANN] Media Summit at ELCE Dublin, September 12: Draft Agenda V2
Date: Mon, 5 Sep 2022 17:44:26 +0300	[thread overview]
Message-ID: <YxYLSk2pKdGnNDP3@pendragon.ideasonboard.com> (raw)
In-Reply-To: <YxX8dzSsquJmO5hP@paasikivi.fi.intel.com>

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@ideasonboard.com>

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.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2022-09-05 14:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 10:53 [ANN] Media Summit at ELCE Dublin, September 12: Draft Agenda V2 Hans Verkuil
2022-08-24 18:13 ` Nicolas Dufresne
2022-08-25 14:29   ` Nicolas Dufresne
2022-09-05 13:41 ` Sakari Ailus
2022-09-05 14:44   ` Laurent Pinchart [this message]
2022-09-05 14:56     ` Ricardo Ribalda
2022-09-05 15:08       ` Jernej Škrabec
2022-09-06  6:58     ` Hans Verkuil
2022-09-07  6:51     ` Hans Verkuil
2022-09-07  7:44       ` Sakari Ailus
2022-09-07  9:51       ` Laurent Pinchart
2022-09-07  9:58         ` Hans Verkuil
2022-09-07 10:06           ` Laurent Pinchart
2022-09-07 10:30             ` Hans Verkuil
2022-09-07 11:53               ` Maxime Ripard
2022-09-07  7:36     ` Sakari Ailus
2022-09-07  7:44       ` Laurent Pinchart
2022-09-07 12:01         ` Sakari Ailus
2022-09-07 11:53     ` Maxime Ripard
2022-09-30 20:46       ` Maxime Ripard
2022-09-30 20:52         ` Laurent Pinchart
2022-10-01 10:07           ` Maxime Ripard
2022-10-03  0:20             ` Laurent Pinchart
2022-10-10  8:26               ` Maxime Ripard
2022-09-07 12:46     ` Kieran Bingham
2022-09-08  8:47       ` Jacopo Mondi
2022-09-10  4:23     ` Chen-Yu Tsai
2022-09-10 11:18     ` Laurent Pinchart
2022-09-22 22:05   ` Sakari Ailus

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=YxYLSk2pKdGnNDP3@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=djrscally@gmail.com \
    --cc=hidenorik@chromium.org \
    --cc=hverkuil@xs4all.nl \
    --cc=jacopo@jmondi.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=maxime@cerno.tech \
    --cc=nicolas@ndufresne.ca \
    --cc=p.zabel@pengutronix.de \
    --cc=paul.kocialkowski@bootlin.com \
    --cc=ribalda@chromium.org \
    --cc=sakari.ailus@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox