> * $smime_default_key is used for self encryption and signing
> * $smime_sign_as overrides $smime_default_key for signing
> * $smime_is_default
> * $smime_self_encrypt
>
> Note the GPGME backend stores certs differently, and does not use the
> same IDs as the traditional backend. The gppsm
On Tue, Jun 16, 2020 at 07:37:01PM -0400, Josef 'Jeff' Sipek wrote:
I few months ago, I ran into a pgp_sign_as + GPGME related issue: Setting
it to a subkey doesn't work. Not using GPGME (and using gpg.rc instead)
works. IIRC, that was a GPGME API limitation.
Did anything change about that?
On Sun, Jun 14, 2020 at 10:00:52 -0700, Kevin J. McCarthy wrote:
> On Sun, Jun 14, 2020 at 12:20:22PM +0100, isdtor wrote:
> >Two questions remain now. The first, when using mutt with gpgme, are
> >any of the gpg/gpg/certificate/smime related configuration variables
> >still relevant? And if so,
Kevin J. McCarthy writes:
> On Sun, Jun 14, 2020 at 12:20:22PM +0100, isdtor wrote:
> >Two questions remain now. The first, when using mutt with gpgme, are
> >any of the gpg/gpg/certificate/smime related configuration variables
> >still relevant? And if so, which? The question arises from this
On Sun, Jun 14, 2020 at 12:20:22PM +0100, isdtor wrote:
Two questions remain now. The first, when using mutt with gpgme, are
any of the gpg/gpg/certificate/smime related configuration variables
still relevant? And if so, which? The question arises from this
comment,
I don't use S/MIME
I'm very close to a usable setup for S/MIME. It took a lot of research, the
documentation isn't great and seems a bit outdated in some cases
(https://gitlab.com/muttmua/mutt/-/wikis/MuttGuide/UseSMIME - patch gpgme?),
but the basics work.
Two questions remain now. The first, when using mutt
