Re: Refactoring of mml1991.el, mml2015.el, mml-smime.el

[Jens Lechtenboerger <jens.lechtenboerger@fsfe.org>]

On 2015-10-18, at 10:09, Greg Troxel wrote:

> Jens Lechtenboerger <jens.lechtenboerger@fsfe.org> 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’s README, “2.0 is the current stable version for general use”,
>> while “1.4 is the old standalone version which is most suitable for
>> older or embedded platforms.”
>> 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’m sorry for that wording.  Dropping the “not” seems better.

> So if you mean:
>
>   within elisp code in gnus/epg/etc. we should remove the code that
>   caches passphrases

I’d 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’m not sure how many people use caching inside Emacs.  Let’s wait
for comments here.

Best wishes
Jens