Re: modern Wanderlust + gpg2 (GnuPG 2.2+) configuration
"Greg A. Woods" <[email protected]> Sat, 08 Dec 2018 15:21:57 -0800
| Newsgroups | gmane.mail.wanderlust.general |
|---|---|
| Organization | Planix, Inc. |
| Message-ID | <m1gVlv3-0036tP0__40209.5791804188$1544311374$gmane$org@more.local> |
At Fri, 09 Nov 2018 13:55:51 -0800, "Greg A. Woods" <[email protected]> wrote: Subject: Re: modern Wanderlust + gpg2 (GnuPG 2.2+) configuration > > I couldn't find anything useful anywhere about configuring EasyPG with > any SEMI version. So I still can't find anything _useful_, but I'm slowly learning more about EasyPG (and epa, etc., etc., etc.) by reading miles of elisp. I'm hugely missing PGG though. This EasyPG is anything but. It's like stepping back into the dark ages of PGP when it first arrived, but with a Windoze wrapper on it all. I'm seriously thinking of hacking SEMI to use PGG again unless someone can help with at least the following very serious UX issues: - how do I do the equivalent of pgg-fetch-key in EasyPG? - how do I get SEMI/EasyPG to choose the most appropriate default signing key based on the "From:" header? Less serious are things like the new fixed/frozen policy-first B.S. (instead of simply providing "mechanisms for policies with good defaults") in both EasyPG/epa and Emacs in general (sort of like the same B.S. in Chrome). For example I can't easily and separately decide whether it's OK to not hide my passphrase while typing it, and yet still hide my IMAP password. PGG had a simple hook via pgg-read-passphrase. Hacking EasyPG to add these features seems harder than reverting to PGG and getting it to work nicely again with GPG-2.2 et al. Also, how do I get SEMI to always sign all messages by default? -- Greg A. Woods <[email protected]> +1 250 762-7675 RoboHack <[email protected]> Planix, Inc. <[email protected]> Avoncote Farms <[email protected]>