Discussion:
GnuPG signature
(too old to reply)
Anonymous
2021-09-15 08:01:20 UTC
Permalink
How to switch mutt on old-style clearsign signature?
Tavis Ormandy
2021-09-16 01:09:05 UTC
Permalink
Post by Anonymous
How to switch mutt on old-style clearsign signature?
Hmm, are you asking for how to *send* clearsign signatures or how to
*check* them? If it's the latter, I think you want `set pgp_auto_decode`.

Tavis.
--
_o) $ lynx lock.cmpxchg8b.com
/\\ _o) _o) $ finger ***@sdf.org
_\_V _( ) _( ) @taviso
Anonymous
2021-09-16 12:28:56 UTC
Permalink
Post by Tavis Ormandy
Post by Anonymous
How to switch mutt on old-style clearsign signature?
Hmm, are you asking for how to *send* clearsign signatures or how to
*check* them? If it's the latter, I think you want `set
pgp_auto_decode`.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I mean how to send clear signed message?
Friedhelm Waitzmann
2021-11-11 16:21:04 UTC
Permalink
Post by Anonymous
Post by Tavis Ormandy
Post by Anonymous
How to switch mutt on old-style clearsign signature?
Hmm, are you asking for how to *send* clearsign signatures or how to
*check* them? If it's the latter, I think you want `set
pgp_auto_decode`.
I mean how to send clear signed message?
Set crypt_use_gpgme to »no«. From muttrc(5):

crypt_use_gpgme
Type: boolean
Default: no

This variable controls the use of the
GPGME-enabled crypto backends. If it is set and
Mutt was built with gpgme support, the gpgme code
for S/MIME and PGP will be used instead of the
classic code. Note that you need to set this
option in .muttrc; it won't have any effect when
used interactively.

Note that the GPGME backend does not support
creating old-style inline (traditional) PGP
encrypted or signed messages (see
$pgp_autoinline).

And set pgp_clearsign_command accordingly to the command string
that will do the clearsigning.


Friedhelm

Continue reading on narkive:
Loading...