From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daiki Ueno Newsgroups: gmane.emacs.devel Subject: Re: ELPA security Date: Sat, 29 Jun 2013 01:15:17 +0900 Message-ID: <87sj026wkq.fsf-ueno@gnu.org> 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> <87ip77y2s9.fsf@Rainer.invalid> <874ncintdi.fsf@lifelogs.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1372436130 28175 80.91.229.3 (28 Jun 2013 16:15:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 28 Jun 2013 16:15:30 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 28 18:15:32 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 1UsbKc-0005LW-PC for ged-emacs-devel@m.gmane.org; Fri, 28 Jun 2013 18:15:30 +0200 Original-Received: from localhost ([::1]:35487 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsbKc-0003HU-96 for ged-emacs-devel@m.gmane.org; Fri, 28 Jun 2013 12:15:30 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48633) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsbKX-0003HJ-7a for emacs-devel@gnu.org; Fri, 28 Jun 2013 12:15:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UsbKU-0002yf-KB for emacs-devel@gnu.org; Fri, 28 Jun 2013 12:15:25 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:38456) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsbKU-0002ya-H1 for emacs-devel@gnu.org; Fri, 28 Jun 2013 12:15:22 -0400 Original-Received: from [2001:e41:db5e:fb14::1] (port=49599 helo=debian) by fencepost.gnu.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1UsbKT-0008On-Ty for emacs-devel@gnu.org; Fri, 28 Jun 2013 12:15:22 -0400 In-Reply-To: <874ncintdi.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 28 Jun 2013 11:32:25 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e 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:161242 Archived-At: Ted Zlatanov writes: > Would it be better to follow the steps here than to have a separate > directory? Or maybe we should do a separate key ring AND an alternative > directory? I think using the separate directory only is a bit better here, because of flexibility: 1. users could have separate preference for elpa keys, using gpg.conf or trustdb.gpg in the directory 2. package.el could display which keys are changed/imported in the ring, when the ring (on the web) is changed It might look overkill to have a separate directory, but actually GPGME, on which epg.el is modelled, only provides the directory option. Also some tools follow this way (e.g. caff in Debian signing-party package). Regards, -- Daiki Ueno