Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] MAINTAINERS: Add ED25519 key for tag/commit signing experiment
Date: Wed, 31 Aug 2022 20:57:47 +0200
Message-ID: <20220831185747.GN2088045@pb2> (raw)
In-Reply-To: <20220808154315.GV2088045@pb2>


[-- Attachment #1.1: Type: text/plain, Size: 2343 bytes --]

On Mon, Aug 08, 2022 at 05:43:15PM +0200, Michael Niedermayer wrote:
> On Mon, Aug 08, 2022 at 12:16:36PM -0300, James Almer wrote:
> > On 8/8/2022 11:50 AM, Michael Niedermayer wrote:
> > > From: Michael Niedermayer <michael-git@niedermayer.cc>
> > > 
> > > Signed-off-by: Michael Niedermayer <michael-git@niedermayer.cc>
> > > ---
> > >   MAINTAINERS | 1 +
> > >   1 file changed, 1 insertion(+)
> > > 
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 7ed15f96f6..ed2ec0b90c 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -626,6 +626,7 @@ Leo Izen (thebombzen)         B6FD 3CFC 7ACF 83FC 9137 6945 5A71 C331 FD2F A19A
> > >   Loren Merritt                 ABD9 08F4 C920 3F65 D8BE 35D7 1540 DAA7 060F 56DE
> > >   Lynne                         FE50 139C 6805 72CA FD52 1F8D A2FE A5F0 3F03 4464
> > >   Michael Niedermayer           9FF2 128B 147E F673 0BAD F133 611E C787 040B 0FAB
> > > +                              DD1E C9E8 DE08 5C62 9B3E 1846 B18E 8928 B394 8D64
> > 
> > There is a "FFmpeg release signing key" key already, used for the tarballs,
> > and which you obviously have access to. Can we not use it for the release
> > tags too, instead of a new key to your name? 
> 
> possible
> 
> 
> > It would probably require
> > creating the git tags using the ffmpeg-devel@ffmpeg.org email.
> 
> If the goal is to get a "verified" sticker on github i think that would require
> an account on github too that has a gpg key and email of ffmpeg-devel@ffmpeg.org
> iam not sure about the security implications if a github account uses a
> public mailing list on a secondary email address

also i just noticed that "git tag" seems not to have any option to set the
tagger. I would have to hack the git config to set it to 
ffmpeg-devel@ffmpeg.org, that feels really like iam doing something thats not
supposed to be done. So for 5.1.1 ill stay with the natural thing and just
create the tag, but iam happy to set the tagger and key to anything people
want. Please start a RFC or something if you want so people can discuss
this, i wonder what other projects do ...

thx

[...]



-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Asymptotically faster algorithms should always be preferred if you have
asymptotical amounts of data

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

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2022-08-31 18:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 14:50 [FFmpeg-devel] [RFC] git and signing commits and tags Michael Niedermayer
2022-08-08 14:50 ` [FFmpeg-devel] [PATCH 1/2] MAINTAINERS: Add ED25519 key for tag/commit signing experiment Michael Niedermayer
2022-08-08 15:16   ` James Almer
2022-08-08 15:43     ` Michael Niedermayer
2022-08-31 18:57       ` Michael Niedermayer [this message]
2022-08-09 19:33   ` Michael Niedermayer
2022-08-08 14:50 ` [FFmpeg-devel] [PATCH 2/2] doc/git-howto.texi: Document commit signing Michael Niedermayer
2022-08-08 15:02 ` [FFmpeg-devel] [RFC] git and signing commits and tags James Almer
2022-08-08 15:58   ` Michael Niedermayer
     [not found] ` <20220808145008.26162-1-michael@niedermayer.cc-N8xvyjN----2>
2022-08-08 19:26   ` Lynne
2022-08-08 22:36     ` Michael Niedermayer
2022-08-09 10:59       ` Michael Niedermayer
2022-08-09 11:02         ` Michael Niedermayer
2022-08-09 17:50           ` Lynne
2022-08-09 19:32             ` Michael Niedermayer
2022-08-09 11:22     ` Gerion Entrup

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=20220831185747.GN2088045@pb2 \
    --to=michael@niedermayer.cc \
    --cc=ffmpeg-devel@ffmpeg.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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git