From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1EtbfH-0005Sy-0y for garchives@archives.gentoo.org; Tue, 03 Jan 2006 02:12:43 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k032BsGh010790; Tue, 3 Jan 2006 02:11:54 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k0329kdS013018 for ; Tue, 3 Jan 2006 02:09:46 GMT Received: from 193-172.dsl1.guernsey.net ([213.133.193.172] helo=pohl.lj.net) by smtp.gentoo.org with esmtpa (Exim 4.54) id 1EtbcQ-0000LM-2d for gentoo-dev@lists.gentoo.org; Tue, 03 Jan 2006 02:09:46 +0000 Date: Tue, 3 Jan 2006 02:09:39 +0000 From: Tom Martin To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] developer keyring? Message-ID: <20060103020939.7f70ac85@pohl.lj.net> In-Reply-To: <1136229046.23404.133.camel@localhost> References: <1136229046.23404.133.camel@localhost> X-Mailer: Sylpheed-Claws 2.0.0-rc1 (GTK+ 2.8.9; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_WwJZqxd/hEIZ_3LLW+8.zNn"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Archives-Salt: 0481a837-7871-445f-83f3-3fa2e3f9dea3 X-Archives-Hash: d3bc62466679416dd7ad9f32a47713e9 --Sig_WwJZqxd/hEIZ_3LLW+8.zNn Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 02 Jan 2006 20:10:46 +0100 Patrick Lauer wrote: > So right now you'd have to go through the website (fetch the keys from > the roll-call page ... if you remember where that is) and import them > one by one (time-consuming). >=20 > Any automation of that process would be really appreciated :-) > (Also it would make any mandatory ebuild signing much easier to handle > from a user p.o.v. ...) Shouldn't really be a problem. Grep the key ids from roll-call.xml (any string beginning with "0x") and gpg --recv-keys them. As a side-affect, you should easily be able to find any developers who haven't uploaded their keys to a sensible keyserver, i.e. subkeys.pgp.net. HTH, --=20 Tom Martin, http://dev.gentoo.org/~slarti AMD64, net-mail, shell-tools, vim, recruiters Gentoo Linux --Sig_WwJZqxd/hEIZ_3LLW+8.zNn Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDudzmj5KihLXE/4kRAqEYAKDnh4RUocvHxTnbHqhDtp5w/q6WBgCgwsWU ZeF7N+va/LO8eb1foF3l7XM= =cRzW -----END PGP SIGNATURE----- --Sig_WwJZqxd/hEIZ_3LLW+8.zNn-- -- gentoo-dev@gentoo.org mailing list