From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Darrington Subject: Re: Bad signature on commit 6a34f4ccc8a5d (gnu: python-prompt-toolkit: Update to 1.0.9.) Date: Thu, 29 Dec 2016 07:08:18 +0100 Message-ID: <20161229060818.GA29613@jocasta.intra> References: <20161229021015.GA16162@jasmine> <3cd2cda0-e1c7-9b6d-b04c-b31302a0fe45@tobias.gr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48627) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cMTt9-0004cI-Qb for guix-devel@gnu.org; Thu, 29 Dec 2016 01:08:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cMTt5-0001HT-O2 for guix-devel@gnu.org; Thu, 29 Dec 2016 01:08:31 -0500 Received: from de.cellform.com ([88.217.224.109]:52008 helo=jocasta.intra) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cMTt5-0001Gq-Fq for guix-devel@gnu.org; Thu, 29 Dec 2016 01:08:27 -0500 Content-Disposition: inline In-Reply-To: <3cd2cda0-e1c7-9b6d-b04c-b31302a0fe45@tobias.gr> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Tobias Geerinckx-Rice Cc: guix-devel@gnu.org --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 29, 2016 at 03:49:51AM +0100, Tobias Geerinckx-Rice wrote: Leo, =20 On 29/12/16 03:10, Leo Famulari wrote: > gpg: BAD signature from "Tobias Geerinckx-Rice " =20 Oh dear. =20 > Does anyone else get the same result? Any ideas? =20 I do, so it's a real?? corrupted signature. =20 Looking back, it turns out that this isn't the first time this has happened: another commit of mine (7d162df, gnu: mcelog: Update to 146.) also has a bad signature, which I probably missed for the same reason. =20 How did these commits get into the repository? Our repository is=20 configured to reject unsigned commits. Can it be that it doesn't actually check that the signature matches? !!! --=20 Avoid eavesdropping. Send strong encrypted email. PGP Public key ID: 1024D/2DE827B3=20 fingerprint =3D 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 See http://sks-keyservers.net or any PGP keyserver for public key. --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlhkqFIACgkQimdxnC3oJ7Mj+ACfdQZJ7iHZk1Iec8ow5maq2PCx 7DcAn2G9QuQeUgXuRoVKQfJp0VkOtF3X =vbuu -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK--