From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: Email encryption with S/MIME or OpenPGP?
Date: Thu, 27 Mar 2014 10:57:13 +0100 [thread overview]
Message-ID: <87a9ccdkw6.fsf@gilgamesch.quim.ucm.es> (raw)
In-Reply-To: <m24n2l0y2l.fsf@krugs.de>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
>> "Rainer" == Rainer M Krug <Rainer> writes:
>>
>> You mean using openssl , as described in emacs-wiki? I tried this
>> out and I reached the point of not using smime at all, since it was so
>> cumbersome, till I learned about easyPF and ggpsm. :-D
> That is what I am trying to get to work - but somehow I am struggling.
> Is somebody using here s/mime on a mac via easyPF and gpgsm from
> homebrew? I get the error when calling gpgsm from the commandline:
> ,----
> | $ gpgsm -s
> | gpgsm: certificate is not usable for signing
> | gpgsm: certificate is not usable for signing
> | gpgsm: certificate is not usable for signing
> | gpgsm: note: non-critical certificate policy not allowed
> | gpgsm: can't connect to the dirmngr: IPC connect call failed
> | gpgsm: certificate #1F134CE9BDA747F504F32D21E06EC854/CN=COMODO
> | Client Authentication and Secure Email CA,O=COMODO CA
> | Limited,L=Salford,ST=Greater Manchester,C=GB
> | gpgsm: checking the CRL failed: No dirmngr
> | gpgsm: error creating signature: No dirmngr <GpgSM>
> |
> | $ dirmngr
> | Segmentation fault: 11
> `----
hm your dirmngr is also homebrew? I had some issues with dirmngr on
Ubuntu. Did you try
disable-crl-checks
in your gpgsm conf?
Uwe Brauer
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5556 bytes --]
next prev parent reply other threads:[~2014-03-27 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 8:31 Rainer M Krug
2014-03-19 17:33 ` Uwe Brauer
2014-03-20 14:44 ` Rainer M Krug
2014-03-20 15:33 ` Uwe Brauer
2014-03-25 19:06 ` Uwe Brauer
2014-03-26 15:38 ` Rainer M Krug
2014-03-27 9:57 ` Uwe Brauer [this message]
2014-03-27 10:45 ` Rainer M Krug
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=87a9ccdkw6.fsf@gilgamesch.quim.ucm.es \
--to=oub@mat.ucm.es \
--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).