From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: ELPA security Date: Tue, 08 Jan 2013 18:30:50 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87txqrb6c5.fsf@lifelogs.com> References: <8738zf70ep.fsf@riseup.net> <871uejlbm1.fsf@lifelogs.com> <87k3rrr31g.fsf@Rainer.invalid> <874nium8h0.fsf@lifelogs.com> <87zk0ljaub.fsf@lifelogs.com> <87wqvng299.fsf@lifelogs.com> <87ehhveg4s.fsf@lifelogs.com> <871udvcqgj.fsf@lifelogs.com> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1357687868 4145 80.91.229.3 (8 Jan 2013 23:31:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 8 Jan 2013 23:31:08 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 09 00:31:25 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Tsidf-0001R3-JI for ged-emacs-devel@m.gmane.org; Wed, 09 Jan 2013 00:31:23 +0100 Original-Received: from localhost ([::1]:38591 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsidP-00085N-Ud for ged-emacs-devel@m.gmane.org; Tue, 08 Jan 2013 18:31:07 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:59656) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsidM-00084i-AJ for emacs-devel@gnu.org; Tue, 08 Jan 2013 18:31:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TsidL-0004sc-6l for emacs-devel@gnu.org; Tue, 08 Jan 2013 18:31:04 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:54654) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsidL-0004sS-0H for emacs-devel@gnu.org; Tue, 08 Jan 2013 18:31:03 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TsidX-0001Ee-Gq for emacs-devel@gnu.org; Wed, 09 Jan 2013 00:31:15 +0100 Original-Received: from c-65-96-148-157.hsd1.ma.comcast.net ([65.96.148.157]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 09 Jan 2013 00:31:15 +0100 Original-Received: from tzz by c-65-96-148-157.hsd1.ma.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 09 Jan 2013 00:31:15 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 18 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-65-96-148-157.hsd1.ma.comcast.net X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:l5nedARoRFra49Rnv7ewokpkz+k= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:156170 Archived-At: On Tue, 08 Jan 2013 17:46:51 -0500 Stefan Monnier wrote: SM> I do wonder about key management, tho: the GNU ELPA key (note: not SM> "maintainer" because the key does not belong to any human being) SM> will not last for ever. >> I thought the maintainers would have their own keys, and they would sign >> a GNU ELPA "signing subkey" that's only used for releasing. SM> I'm sufficiently unsophisticated that I don't really know what SM> that means. I understands keys can expire and can be revoked, but that SM> doesn't say how the end-user will deal with such a situation. SM> We need some way to update the signing key in a trustworthy way. OK, I'll prepare a workflow and offer it for public review as part of the POC. Ted