From: "Clemens Schüller" <cs.mlists+gnus@mailbox.org>
To: ding@gnus.org
Subject: Re: Problems with some Messages
Date: Thu, 12 Oct 2017 19:38:02 +0200 [thread overview]
Message-ID: <m2k200w9l1.fsf@warhorse.home.aneadesign.com> (raw)
In-Reply-To: <877ew05o0t.fsf@informationelle-selbstbestimmung-im-internet.de> (Jens Lechtenboerger's message of "Thu, 12 Oct 2017 18:28:18 +0200")
Hello!
Jens Lechtenboerger wrote:
> Which version of gpgsm is that?
--8<---------------cut here---------------start------------->8---
[mente@warhorse: ~]% LANG=C gpgsm --help
gpgsm (GnuPG/MacGPG2) 2.2.0
libgcrypt 1.8.1
libksba 1.3.5
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Home: /Users/mente/.gnupg
Supported algorithms:
Cipher: 3DES, AES128, AES192, AES256, SERPENT128, SERPENT192, SERPENT256, SEED, CAMELLIA128, CAMELLIA192, CAMELLIA256
Pubkey: RSA, ECC
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224, WHIRLPOOL
Syntax: gpgsm [options] [files]
Sign, check, encrypt or decrypt using the S/MIME protocol
Default operation depends on the input data
--8<---------------cut here---------------end--------------->8---
> Variable epg-config--program-alist lists the minimum required
> version.
--8<---------------cut here---------------start------------->8---
epg-config--program-alist is a variable defined in ‘epg-config.el’.
Its value is
((OpenPGP epg-gpg-program
("gpg2" . "2.1.6")
("gpg" . "1.4.3"))
(CMS epg-gpgsm-program
("gpgsm" . "2.0.4")))
--8<---------------cut here---------------end--------------->8---
> Maybe customizing (not setting) epg-gpgsm-program to the full path
> of your gpgsm binary helps.
Thanks for the hint - this solution works.
--8<---------------cut here---------------start------------->8---
[mente@warhorse: ~]% dir =gpgsm
-rwxr-xr-x 1 root admin 484900 22 Sep 20:56 /usr/local/MacGPG2/bin/gpgsm
--8<---------------cut here---------------end--------------->8---
I think, the non standard path was the problem.
--
Best Regards, Clemens Schüller
prev parent reply other threads:[~2017-10-12 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 9:39 Clemens Schüller
2017-10-11 9:47 ` Clemens Schüller
2017-10-11 11:06 ` Marcus Frings
2017-10-11 17:41 ` Clemens Schüller
2017-10-12 16:28 ` Jens Lechtenboerger
2017-10-12 17:38 ` Clemens Schüller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2k200w9l1.fsf@warhorse.home.aneadesign.com \
--to=cs.mlists+gnus@mailbox.org \
--cc=cs.mlists@mailbox.org \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).