From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/86233 Path: news.gmane.org!not-for-mail From: Jens Lechtenboerger Newsgroups: gmane.emacs.gnus.general Subject: Re: Refactoring of mml1991.el, mml2015.el, mml-smime.el Date: Mon, 19 Oct 2015 14:58:15 +0200 Message-ID: <87wpuj817c.fsf@informationelle-selbstbestimmung-im-internet.de> References: <86wq8xffpv.fsf@informationelle-selbstbestimmung-im-internet.de> <87k2qmsrt1.fsf@informationelle-selbstbestimmung-im-internet.de> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1445259597 17815 80.91.229.3 (19 Oct 2015 12:59:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 19 Oct 2015 12:59:57 +0000 (UTC) Cc: ding@gnus.org To: Greg Troxel Original-X-From: ding-owner+M34467@lists.math.uh.edu Mon Oct 19 14:59:44 2015 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from lists1.math.uh.edu ([129.7.128.208]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZoA2R-0008WU-Br for ding-account@gmane.org; Mon, 19 Oct 2015 14:59:43 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.85) (envelope-from ) id 1ZoA1G-0000bv-6c; Mon, 19 Oct 2015 07:58:30 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.85) (envelope-from ) id 1ZoA1D-0000bT-Rt for ding@lists.math.uh.edu; Mon, 19 Oct 2015 07:58:27 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from ) id 1ZoA1B-0007Jb-TF for ding@lists.math.uh.edu; Mon, 19 Oct 2015 07:58:27 -0500 Original-Received: from mx1.mailbox.org ([80.241.60.212]) by quimby.gnus.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1ZoA19-0000cH-VI for ding@gnus.org; Mon, 19 Oct 2015 14:58:24 +0200 Original-Received: from smtp1.mailbox.org (smtp1.mailbox.org [80.241.60.240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.mailbox.org (Postfix) with ESMTPS id 5EDFE43E0C; Mon, 19 Oct 2015 14:58:18 +0200 (CEST) X-Virus-Scanned: amavisd-new at heinlein-support.de Original-Received: from smtp1.mailbox.org ([80.241.60.240]) by gerste.heinlein-support.de (gerste.heinlein-support.de [91.198.250.173]) (amavisd-new, port 10030) with ESMTP id V9KycK_coXgd; Mon, 19 Oct 2015 14:58:17 +0200 (CEST) OpenPGP: id=0xA142FD84; url=http://www.informationelle-selbstbestimmung-im-internet.de/A142FD84.asc Mail-Followup-To: Greg Troxel , ding@gnus.org In-Reply-To: (Greg Troxel's message of "Sun, 18 Oct 2015 10:09:32 -0400") User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.0.50 (gnu/linux) X-Spam-Score: -4.9 (----) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:86233 Archived-At: On 2015-10-18, at 10:09, Greg Troxel wrote: > Jens Lechtenboerger writes: >> In fact, one of my test cases >> (mml-epg-en-decrypt-passphrase-no-cache-smime-todo) >> has an expected failure for gpgsm, as the cache is not inspected. >> Another test case (mml-epg-en-decrypt-passphrase-no-cache-openpgp-todo) >> is skipped for GnuPG 2.x. >> Is there a way to cache passphrases within Emacs, even with gpgsm and >> GnuPG 2.x? > > Are you saying that you think it is a good idea to cache passphrases > within emacs, for general use, or to enable tests? I tried to enable that for testing, but failed. >> Note that GnuPG 2.x is where the development happens, and according to >> GnuPG=E2=80=99s README, =E2=80=9C2.0 is the current stable version for g= eneral use=E2=80=9D, >> while =E2=80=9C1.4 is the old standalone version which is most suitable = for >> older or embedded platforms.=E2=80=9D >> So, if we cannot cache for the current stable version, should we not >> recommend caching inside gpg-agent in general and get rid of the >> associated code? Even if there was a way, should we not recommend >> caching inside gpg-agent in general? > > I'm having a little trouble following "should we not". I=E2=80=99m sorry for that wording. Dropping the =E2=80=9Cnot=E2=80=9D see= ms better. > So if you mean: > > within elisp code in gnus/epg/etc. we should remove the code that > caches passphrases I=E2=80=99d like to hear opinions on that. > we should expect people to use gnupg's gpg-agent(1) program to deal > with caching if they want to cache, including telling people to do > that with gnupg1. That would be my preference, yes. > we should realize that openssl-based mime will not have any caching in > emacs or externally, but that's ok because that code is or will be > deprecated soon I=E2=80=99m not sure how many people use caching inside Emacs. Let=E2=80= =99s wait for comments here. Best wishes Jens