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 C188743D5C for ; Tue, 9 Aug 2022 11:00:03 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id C402C68B7FC; Tue, 9 Aug 2022 14:00:00 +0300 (EEST) Received: from relay1-d.mail.gandi.net (relay1-d.mail.gandi.net [217.70.183.193]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 0435268B58E for ; Tue, 9 Aug 2022 13:59:53 +0300 (EEST) Received: (Authenticated sender: michael@niedermayer.cc) by mail.gandi.net (Postfix) with ESMTPSA id 1D85E240004 for ; Tue, 9 Aug 2022 10:59:52 +0000 (UTC) Date: Tue, 9 Aug 2022 12:59:52 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20220809105952.GY2088045@pb2> References: <20220808145008.26162-1-michael@niedermayer.cc> <20220808145008.26162-1-michael@niedermayer.cc-N8xvyjN----2> <20220808223653.GX2088045@pb2> MIME-Version: 1.0 In-Reply-To: <20220808223653.GX2088045@pb2> 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="===============8677296236811633499==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============8677296236811633499== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="+1tcKVLXPU0QafK6" Content-Disposition: inline --+1tcKVLXPU0QafK6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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/recomma= nd > > > 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/75f196acd16fb0c0ca7a94f0c6= 6072e7c6f736bf > > > > > > 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 keyservers i c= hecked 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 FE50139C680572CAFD521F8= DA2FEA5F03F034464 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 [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Homeopathy is like voting while filling the ballot out with transparent ink. Sometimes the outcome one wanted occurs. Rarely its worse than filling out a ballot properly. --+1tcKVLXPU0QafK6 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCYvI+IwAKCRBhHseHBAsP q2IqAJkBegaRpOEDqk8GARBE6ZDCc1jwuwCeMlQP0GgFF/M1rH4ll9Krl9wCP/E= =x0RB -----END PGP SIGNATURE----- --+1tcKVLXPU0QafK6-- --===============8677296236811633499== 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". --===============8677296236811633499==--