From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id AD09D43D81 for ; Tue, 9 Aug 2022 19:32:51 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 5A97868B7C0; Tue, 9 Aug 2022 22:32:47 +0300 (EEST) Received: from relay7-d.mail.gandi.net (relay7-d.mail.gandi.net [217.70.183.200]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id D3D5668B5C5 for ; Tue, 9 Aug 2022 22:32:40 +0300 (EEST) Received: (Authenticated sender: michael@niedermayer.cc) by mail.gandi.net (Postfix) with ESMTPSA id 21B6F20003 for ; Tue, 9 Aug 2022 19:32:39 +0000 (UTC) Date: Tue, 9 Aug 2022 21:32:39 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20220809193239.GA2088045@pb2> References: <20220808145008.26162-1-michael@niedermayer.cc> <20220808145008.26162-1-michael@niedermayer.cc-N8xvyjN----2> <20220808223653.GX2088045@pb2> <20220809105952.GY2088045@pb2> <20220809110235.GZ2088045@pb2> MIME-Version: 1.0 In-Reply-To: Subject: Re: [FFmpeg-devel] [RFC] git and signing commits and tags X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: multipart/mixed; boundary="===============0183094023559913138==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============0183094023559913138== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="DG78IEnUmLKoW088" Content-Disposition: inline --DG78IEnUmLKoW088 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 09, 2022 at 07:50:13PM +0200, Lynne wrote: > Aug 9, 2022, 13:02 by michael@niedermayer.cc: >=20 > > 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: > >> > >=20 > >> > > > Given the recent server issues, i wonder if we should suggest/re= command > >> > > > and document signing commits and tags > >> > > > > >> > > > i tried to push such commit to github and it nicely says "verifi= ed" > >> > > > https://github.com/michaelni/FFmpeg/commit/75f196acd16fb0c0ca7a9= 4f0c66072e7c6f736bf > >> > > > > >> > > > 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. > >> > > > > >> > >=20 > >> > > I sign all of my commits,=20 > >> >=20 > >> > I didnt notice, but thats good as it also proofs it works with no ill > >> > sideeffects > >> >=20 > >> > Where can i find your public key ? it seems its not on the keyserver= s i checked > >> > >> Your key seems only on openpgp.org but that strips userids unless the = owner approves it=20 > >> (i presume for GDPR) making the key not work > >> > >> gpg --keyserver hkps://keys.openpgp.org --recv-keys FE50139C680572CAFD= 521F8DA2FEA5F03F034464 > >> 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 > > >=20 > 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 20= 19, > but that server also seems like it's forgotten my key and not accepting i= t. yes, i was also scratching my head yesterday about this keyserver apocalypse the script below was what i ended up writing but iam not sure its usefull #!/bin/bash gpg --keyserver hkps://pgp.mit.edu --recv-keys $* & gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys $* & gpg --keyserver hkps://keys.openpgp.org --recv-keys $* & gpg --keyserver hkps://keys.gnupg.net --recv-keys $* & gpg --keyserver hkps://keyserver.pgp.com --recv-keys $* & >=20 > 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 f= rom 2001! > Maybe we should clean up the list of keys. yes maybe we also should collect the full public keys and not just the hashes this list of hashes came from a time where obtaining a key from a hash was trivial thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Take away the freedom of one citizen and you will be jailed, take away the freedom of all citizens and you will be congratulated by your peers in Parliament. --DG78IEnUmLKoW088 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCYvK2UwAKCRBhHseHBAsP q0ZpAJ9zz9UFZx9cZ7uTt/UGaMMz5YoBawCfUj9PR/wUEEesrFNe8AERepyuxQ0= =osYs -----END PGP SIGNATURE----- --DG78IEnUmLKoW088-- --===============0183094023559913138== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============0183094023559913138==--