[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bad signature on commit 6a34f4ccc8a5d (gnu: python-prompt-toolkit: U
|
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 |
|
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On Thu, Dec 29, 2016 at 03:49:51AM +0100, Tobias Geerinckx-Rice wrote:
Leo,
On 29/12/16 03:10, Leo Famulari wrote:
> gpg: BAD signature from "Tobias Geerinckx-Rice <address@hidden>"
Oh dear.
> Does anyone else get the same result? Any ideas?
I do, so it's a real?? corrupted signature.
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.
How did these commits get into the repository? Our repository is
configured to reject unsigned commits. Can it be that it doesn't
actually check that the signature matches? !!!
--
Avoid eavesdropping. Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
signature.asc
Description: Digital signature