Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] git and signing commits and tags
Date: Tue, 9 Aug 2022 19:50:13 +0200 (CEST)
Message-ID: <N92ibp5--3-2@lynne.ee> (raw)
In-Reply-To: <20220809110235.GZ2088045@pb2>

Aug 9, 2022, 13:02 by michael@niedermayer.cc:

> On Tue, Aug 09, 2022 at 12:59:52PM +0200, Michael Niedermayer wrote:
>
>> On Tue, Aug 09, 2022 at 12:36:53AM +0200, Michael Niedermayer wrote:
>> > On Mon, Aug 08, 2022 at 09:26:52PM +0200, Lynne wrote:
>> > > Aug 8, 2022, 16:50 by michael@niedermayer.cc:
>> > > 
>> > > > Given the recent server issues, i wonder if we should suggest/recommand
>> > > > and document signing commits and tags
>> > > >
>> > > > i tried to push such commit to github and it nicely says "verified"
>> > > > https://github.com/michaelni/FFmpeg/commit/75f196acd16fb0c0ca7a94f0c66072e7c6f736bf
>> > > >
>> > > > Ive generated a new gpg key for this experiment as i dont have my
>> > > > main key on the box used for git development and also using more
>> > > > modern eliptic curve stuff (smaller keys & sigs)
>> > > > i will upload this key to the keyservers in case it becomes the
>> > > > one i use for git.
>> > > >
>> > > 
>> > > I sign all of my commits, 
>> > 
>> > I didnt notice, but thats good as it also proofs it works with no ill
>> > sideeffects
>> > 
>> > Where can i find your public key ? it seems its not on the keyservers i checked
>>
>> Your key seems only on openpgp.org but that strips userids unless the owner approves it 
>> (i presume for GDPR) making the key not work
>>
>> gpg --keyserver hkps://keys.openpgp.org --recv-keys FE50139C680572CAFD521F8DA2FEA5F03F034464
>> gpg: key A2FEA5F03F034464: no user ID
>> gpg: Total number processed: 1
>>
>> gpg --list-keys FE50139C680572CAFD521F8DA2FEA5F03F034464
>> gpg: error reading key: No public key
>>
>> gpg --recv-keys FE50139C680572CAFD521F8DA2FEA5F03F034464
>> gpg: keyserver receive failed: No data
>>
>
> found your key with google here:
> https://lynne.ee/extra/A2FEA5F03F034464.asc
>

I just pushed it to keyserver.ubuntu.com, the only still working server
I found, surprisingly. Seems a few months ago sks (a protocol/sever?
to share keys between servers) was deprecated and most servers went
down, and the GDPR also took some out. Sad. There's some work done
to make a new protocol/server apparently.
I'm very sure I pushed my key to the MIT server back when I made it in 2019,
but that server also seems like it's forgotten my key and not accepting it.

I once imported all maintainer keys listed in MAINTAINERS and found many
were revoked (I think compn's), while some used triple DES. The oldest key
I found for a maintainer is actually Nicolas George's key, a triple DES from 2001!
Maybe we should clean up the list of keys.
_______________________________________________
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-09 17:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 14:50 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
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 [this message]
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=N92ibp5--3-2@lynne.ee \
    --to=dev@lynne.ee \
    --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