Hi, On Sunday, 2015-07-05 13:40:43 -0700, Brendan Cully wrote:
> Older GPGMEs are missing CMS (S/MIME) support. Don't force the poor
> users to hit enter every time they start mutt.
What is "older" exactly? And could we assume that anyone using a recent
mutt would not be using such "older" GPGME? Instead, wouldn't be
checking the GPGME version number and only suppressing the confirmation
if it is known to be "older" a more user friendly approach, so actually
wait for a key when the GPGME version is expected to support CMS but
does not?
Anyhow, this ...
> if (gpgme_engine_check_version (GPGME_PROTOCOL_OpenPGP) !=
> GPG_ERR_NO_ERROR)
> {
> mutt_error (_("GPGME: OpenPGP protocol not available"));
> - if (mutt_any_key_to_continue (NULL) == -1)
> - mutt_exit(1);
... removing also the OpenPGP check failure confirmation doesn't look
very appealing to me, the error message will just fly by and may get
unnoticed while GPGME is really expected to support OpenPGP.
Eike
--
OpenPGP/GnuPG encrypted mail preferred in all private communication.
Key "ID" 0x65632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A
Better use 64-bit 0x6A6CD5B765632D3A here is why: https://evil32.com/
Care about Free Software, support the FSFE https://fsfe.org/support/?erack
Use LibreOffice! https://www.libreoffice.org/
signature.asc
Description: PGP signature
