From: Gijs Hillenius <gijs@hillenius.net>
To: 24718@debbugs.gnu.org
Cc: Andreas Schwab <schwab@suse.de>, Daiki Ueno <ueno@gnu.org>
Subject: bug#24718: gpgsm takes (too) long (was: bug#24718: emacs25.1 + gnus, opening message gives: epg-error "no usable configuration" CMS, bug#24718: 25.1; (auth-source-search) fails in 25.1.1 for OSX)
Date: Fri, 21 Oct 2016 09:57:21 +0200 [thread overview]
Message-ID: <87y41i3zj2.fsf@hillenius.net> (raw)
In-Reply-To: <CAKE5LL6Z8TC1A7hROF6xrS0c2OvvUPsB_kw8fEHHGULiA0VoYA@mail.gmail.com>
On 20 Oct 2016, Andreas Schwab wrote:
> On Okt 20 2016, Gijs Hillenius <gijs@hillenius.net> wrote:
>
>> On 20 Oct 2016, Daiki Ueno wrote:
>>
>>>> Well, that explains something :-) I did not before have this gpgsm
>>>> installed. Now I have, but oddly, now gnus takes forever to open
>>>> the message.
>>>
>>> S/MIME signature verification with gpgsm could take some time. If
>>> it takes really too long, a usual suggestion is to gather debug
>>> output with (setq epg-debug t).
>>
>> it takes many minutes.. and I give up waiting, so press C-g
>
> Perhaps it needs to download the CRL, which can take a long time.
> Watch the directory ~/.gnupg/dirmngr-cache.d while it hangs.
Thanks!
On Debian, that dir seems to be called ~/.gnupg/crls.d/
Tried opening one of these messages again: and yesterday gave it more
than 30 minutes before I gave up. ~/.gnupg/crls.d/ now contains a file
(very-long-number.db).
I go to the next s/mime message, and get that question about ultimate
trust again. I say no, and Gnus displays the message with a (valid)
signature, that is unverified (by me). I did not catch the exact output,
sorry.
This happens only once. The next message, from the same sender, this
waiting (verifying) starts again. Even though now there is a file in
~/.gnupg/crls.d/ ?
Is there a way in which I can disable this checking altogether?
Additionally: if no gpgsm is available on the host, perhaps the result
should or could be made similar to what it does in Emacs24, simply
display the message without verification?
next prev parent reply other threads:[~2016-10-21 7:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 18:30 bug#24718: 25.1; (auth-source-search) fails in 25.1.1 for OSX Alexey Veretennikov
2016-10-18 10:03 ` Ted Zlatanov
2016-10-18 22:14 ` Alexey Veretennikov
2016-10-18 13:59 ` bug#24718: emacs25.1 + gnus, opening message gives: epg-error "no usable configuration" CMS Gijs Hillenius
2016-10-19 13:23 ` bug#24718: emacs25.1 + gnus, opening message gives: epg-error "no usable configuration" CMS, bug#24718: 25.1; (auth-source-search) fails in 25.1.1 for OSX Ted Zlatanov
2016-10-19 13:50 ` Gijs Hillenius
2016-10-19 13:56 ` Ted Zlatanov
2016-10-19 15:41 ` Daiki Ueno
2016-10-19 18:27 ` Gijs Hillenius
2016-10-20 7:05 ` Daiki Ueno
2016-10-20 9:02 ` Gijs Hillenius
2016-10-20 9:51 ` Andreas Schwab
2016-10-21 7:57 ` Gijs Hillenius [this message]
2016-10-20 7:20 ` Gijs Hillenius
2016-10-23 7:39 ` Gijs Hillenius
2016-10-27 10:24 ` bug#24718: Fixed: " Gijs Hillenius
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y41i3zj2.fsf@hillenius.net \
--to=gijs@hillenius.net \
--cc=24718@debbugs.gnu.org \
--cc=schwab@suse.de \
--cc=ueno@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).