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: /srv/bzr/emacs/trunk r105466: epa-mail.el handles GnuPG groups. Date: Wed, 17 Aug 2011 10:32:03 +0900 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1313544745 1341 80.91.229.12 (17 Aug 2011 01:32:25 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 17 Aug 2011 01:32:25 +0000 (UTC) Cc: emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 17 03:32:21 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QtUzV-0003xj-1w for ged-emacs-devel@m.gmane.org; Wed, 17 Aug 2011 03:32:21 +0200 Original-Received: from localhost ([::1]:40202 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QtUzS-0006B6-Sg for ged-emacs-devel@m.gmane.org; Tue, 16 Aug 2011 21:32:18 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:41863) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QtUzQ-0006Av-DS for emacs-devel@gnu.org; Tue, 16 Aug 2011 21:32:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QtUzP-0008Dc-Fe for emacs-devel@gnu.org; Tue, 16 Aug 2011 21:32:16 -0400 Original-Received: from ivory4.scn-net.ne.jp ([219.117.176.192]:34735) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1QtUzP-0008DW-0I; Tue, 16 Aug 2011 21:32:15 -0400 Original-Received: from ([192.168.0.187]) (envelope sender: ) by ivory4.scn-net.ne.jp with Active!Hunter esmtp server; Wed, 17 Aug 2011 10:32:12 +0900 Original-Received: Received: from well-done.deisui.org (g187018.scn-net.ne.jp [202.83.187.18]) (authenticated) by blue17.scn-net.ne.jp (unknown) with ESMTP id p7H1WBVI008899; Wed, 17 Aug 2011 10:32:12 +0900 In-Reply-To: (Richard Stallman's message of "Tue, 16 Aug 2011 19:37:05 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-Received-From: 219.117.176.192 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:143342 Archived-At: Richard Stallman writes: > There is already a function `epg-expand-group' to parse group > definitions. With that, the change could be rewritten to: > > Would you please make the improvement you suggested? Done. > Parsing gpg.conf is necessary because epa tries to check the > recipients itself before passing them to gpg. Is there a good reason > to check them? Why not just pass them to gpg (first giving the user > an opportunity to edit the list, as mailcrypt-encrypt does), then let > gpg reject any that are not valid? epa has a nice feature to select keys interactively, which is based on (group-expanded) key information in elisp level. Try: C-u M-x epa-mail-encrypt and you will see the list of keys which will be used to encrypt, before doing actual encryption. This is useful for careful users who don't want to encrypt emails with untrusted/unwanted keys. > This way, epa would not need to expand the groups, or know about them. > And maybe a lot of other code could be deleted too. The amount of code to be removed wouldn't be that much because `epg-expand-group' uses parsed groups info provided by: gpg --list-config --with-config Regards, -- Daiki Ueno