From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: "Neal H. Walfield" Newsgroups: gmane.emacs.devel Subject: Re: epg.el: epg--status-GET_LINE not working? Date: Thu, 06 Jul 2017 21:37:41 +0200 Message-ID: <8737a9we4a.wl-neal@walfield.org> References: <87fuenqlp8.fsf@mithlond.arda> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-Trace: blaine.gmane.org 1499373790 29086 195.159.176.226 (6 Jul 2017 20:43:10 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 6 Jul 2017 20:43:10 +0000 (UTC) User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/24.5 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) Cc: Teemu Likonen , "Neal H. Walfield" , emacs-devel@gnu.org To: Daiki Ueno Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 06 22:43:06 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dTDc7-00079G-03 for ged-emacs-devel@m.gmane.org; Thu, 06 Jul 2017 22:43:03 +0200 Original-Received: from localhost ([::1]:53208 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dTDcC-00046f-GD for ged-emacs-devel@m.gmane.org; Thu, 06 Jul 2017 16:43:08 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53509) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dTCay-0000sX-Fg for emacs-devel@gnu.org; Thu, 06 Jul 2017 15:37:49 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dTCax-0005M5-HC for emacs-devel@gnu.org; Thu, 06 Jul 2017 15:37:48 -0400 Original-Received: from mail.dasr.de ([217.69.77.164]:56995) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dTCat-0005Jb-N4; Thu, 06 Jul 2017 15:37:43 -0400 Original-Received: from p508132ab.dip0.t-ipconnect.de ([80.129.50.171] helo=grit.huenfield.org.walfield.org) by mail.dasr.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1dTCar-0003ct-O4; Thu, 06 Jul 2017 19:37:41 +0000 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 217.69.77.164 X-Mailman-Approved-At: Thu, 06 Jul 2017 16:39:14 -0400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:216247 Archived-At: At Mon, 26 Jun 2017 09:30:00 +0200, Daiki Ueno wrote: > Teemu Likonen writes: > > > I have been thinking of fixing epg.el bug #24350 > > . > > I had a tentative patch for this, but I decided not to include it. > > At that time, the GnuPG developers didn't seem to have a consensus on > how TOFU is supposed to work: FWIW, the TOFU modus operandi are unlikely to change at this stage and have been stable for nearly a year. > Neal suggested it should be triggered by a > key, while Werner suggested that it should be triggered by an email > address. > > I am on Werner's side, and if the things are implemented in that way, we > don't need to handle the conflicts in such lower level (but in the MUA > level). My recollection is that you said: if a recipient is specified by key id rather than by email address (e.g., gpg is called like: 'gpg -e -r KEYID') and the key has a conflict, the conflict should be ignored. You justified this based on the observation that the caller knows what is going on. 1. I disagree that this is the right behavior. 2. AFAIK, there is no precedence for this behavior in gpg. Consider an expired or revoked key: if you try to use it, gpg will error out with "unusable public key."