From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: Re: wrong key used for signing Date: Tue, 28 Mar 2017 15:03:23 +0200 Message-ID: <87y3vptuxw.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> References: <20170328.102506.696688042063031627.post@thomasdanckaert.be> <8760itvldi.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49775) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1csqmX-0008MG-OA for guix-devel@gnu.org; Tue, 28 Mar 2017 09:03:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1csqmU-00074Z-HH for guix-devel@gnu.org; Tue, 28 Mar 2017 09:03:29 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:44632) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1csqmT-00074M-U0 for guix-devel@gnu.org; Tue, 28 Mar 2017 09:03:26 -0400 In-Reply-To: <8760itvldi.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> 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: Thomas Danckaert , guix-devel@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Marius Bakke writes: > Thomas Danckaert writes: > >> I accidentally used the wrong key when signing my commits to=20 >> core-updates yesterday. How can I fix this? A number of commits were=20 >> already made on top of mine, so we'd need to rebase? > > If you can send a signed message (using key D77D54FD according to my > books) containing the public key of the key used to sign these commits > (so they can be verified), I think that is proof enough. Assuming you > admit to making them, of course :-) To be clear, simply "vouching" for the commits in a signed message is good enough for me. It would be good to have the signing key for future reference, but if you don't want to disclose it I'm fine with that. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAljaXxsACgkQoqBt8qM6 VPpGfQgAyycVBkhjabE9l7+L21g/uRka0P28Oog3g09ySCvLE9hN3eDvy4PhkFEn Dv6oQ2V2eHs74QzsN5FBwiTEozKEKVkRizhtYiCDx4pQFHAl8nbmuCEtCqmjp+m2 qxUrg6WpNHqADwdIegyZaZE2xjncyAMBcKZqNfEzSBSkNFSLBpi5MEYOY7PnyvYd dAjAc4jJN/PvmNc4fRnJahOP0QvO1QriYhlX05iAqriNOgjNJySDiJgC8FQapcsP x1D3DzzUboZg9z9Y7p5nQ4Xl7lNv22+vxa04NMAbt5U6cIEejigvudxDBasknd/l e5ai7ZriEa9rUJgYI0V6RiOColcUBA== =JNvZ -----END PGP SIGNATURE----- --=-=-=--