From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: Bad signature on commit 6a34f4ccc8a5d (gnu: python-prompt-toolkit: Update to 1.0.9.) Date: Thu, 29 Dec 2016 01:39:35 -0500 Message-ID: <20161229063935.GA26713@jasmine> References: <20161229021015.GA16162@jasmine> <3cd2cda0-e1c7-9b6d-b04c-b31302a0fe45@tobias.gr> <20161229060818.GA29613@jocasta.intra> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52022) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cMUNK-0000C4-SL for guix-devel@gnu.org; Thu, 29 Dec 2016 01:39:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cMUNH-0000EM-QF for guix-devel@gnu.org; Thu, 29 Dec 2016 01:39:42 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:42067) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cMUNH-0000EB-GE for guix-devel@gnu.org; Thu, 29 Dec 2016 01:39:39 -0500 Content-Disposition: inline In-Reply-To: <20161229060818.GA29613@jocasta.intra> 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: John Darrington Cc: guix-devel@gnu.org --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 29, 2016 at 07:08:18AM +0100, John Darrington wrote: > 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 14= 6.) > also has a bad signature, which I probably missed for the same reaso= n. > =20 >=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? !!! Yes, it's a known limitation: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D22883#129 We need to improve the hook. --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlhkr6MACgkQJkb6MLrK fwiEtw//SEgIApKsqBlddzsHQuLnrNzRtcizoVY+7D5sP1e4KiNibOKn0RdibHoG m1XPLW8XQdxMyXVdcPuzt14Mbrk8t0ZUt6xG1DUQlzX8BkvEWTyFr0zd0rmWlnMi hXW81yAIEs6Kuy3pqSMYMQd89vJcI8JJekqMn2+WCcn0fSIJalUWWseYwuTK0ZZg iyRGkx4nCip1v88ied02qzNTCxzj9yttDOyrkbR0tDP4wtZpaEHlZTJj6/dlMR0K alBGotd5kN8RDZedn0JHgi6QYNWA9wiJDNMJLUllG8UK3LvVu53j8hhSWlq5rVc4 +KXwuYKoyUn0wv8k3sm9KF6tRug8i0reMGN8VE/QbNPrRh8RlOV0uNv1YgiMi31E z2ni4KiThyTKmC/mB5UjItMkzxbVXfjZ6DJFahhToTpb+MOxnYcVy9ndFl5DzFYz LDlTyJLh+ObSse+nItLnxShxJHrPItG0SoKxmyd2YwP12YK5IIybvY5L0C+2iBGj IqCOXhW+vZFTbAb8y3lBRNAu9ucpJcNiFo30SQ6mrfVVXUaNjMlBFmVcXEphR9Tn asn3nwE+K3p6Y2VcHgfSiyGRQWjytwwlENCARfbfNKRJku9mK2irGETqCVYvWCwn jhlBLd79xxJSp2Y0OudGxssVze8AHDvWwH/5zm6CxF8/f+r4ObE= =Gv5h -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62--