From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 1E8B7138334 for ; Thu, 18 Apr 2019 14:31:09 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 22964E0B1D; Thu, 18 Apr 2019 14:20:20 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id EAB9DE0B1C for ; Thu, 18 Apr 2019 14:20:19 +0000 (UTC) Received: from localhost (grandmasfridge.org [45.56.116.213]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: titanofold) by smtp.gentoo.org (Postfix) with ESMTPSA id CA01334187D for ; Thu, 18 Apr 2019 14:20:16 +0000 (UTC) Received: by localhost (Postfix, from userid 1000) id D049D9BF0ADF; Thu, 18 Apr 2019 10:20:12 -0400 (EDT) Date: Thu, 18 Apr 2019 10:20:12 -0400 From: "Aaron W. Swenson" To: gentoo-project@lists.gentoo.org Subject: Re: [gentoo-project] Gentoo Authority Keys are deployed now for testing! Message-ID: <20190418142012.GC8787@gengoff> Mail-Followup-To: gentoo-project@lists.gentoo.org References: <53b2dc8953f3e39a585b7b5720623dc876edd273.camel@gentoo.org> <20190418140421.GB8787@gengoff> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="z4+8/lEcDcG5Ke9S" Content-Disposition: inline In-Reply-To: OpenPGP: url=https://grandmasfridge.org/uploads/pgp-pubkey-0x2153C852F779174F.asc; id=0x2153C852F779174F User-Agent: Mutt/1.10.1 (2018-07-13) X-Archives-Salt: 9d8cb637-9dd0-4577-a6bc-846af712507e X-Archives-Hash: e8b7033f727e2a4d52072496365fa825 --z4+8/lEcDcG5Ke9S Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2019-04-18 16:07, Micha=C5=82 G=C3=B3rny wrote: > You need the primary key to be available in order to create > the certification signature. However, a trick to avoid that is to > create a separate certification key for local-only usage. Just make > sure you won't export it accidentally or use for some other purpose. I'll give that a go. --z4+8/lEcDcG5Ke9S Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iNUEABYKAH0WIQQEC6Ot+QKFRWIXfOT/l1wNKJSl0QUCXLiHnF8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MDQw QkEzQURGOTAyODU0NTYyMTc3Q0U0RkY5NzVDMEQyODk0QTVEMQAKCRD/l1wNKJSl 0d3HAP41bqBQyI2aYPAcAm02qoxtPdhwzlt7V38MkfmaAp2DHQEA6WzXc1qrJWZp AOJxI/5JDnNhn4c64yBOnYPU9yEj1gc= =+Fg4 -----END PGP SIGNATURE----- --z4+8/lEcDcG5Ke9S--