unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [bug?] emacs interface - some mark read tag changes may have failed
Date: Tue, 07 Jun 2022 15:13:25 +0200	[thread overview]
Message-ID: <8735ggk45m.fsf@xelera.eu> (raw)
In-Reply-To: <87mteou77g.fsf@tethera.net>


[-- Attachment #1.1: Type: text/plain, Size: 835 bytes --]

Hi,

David Bremner <david@tethera.net> writes:

[...]

>> Maybe gnupg/dirmngr uses Tor by default if it finds a Tor service on the
>> machine?
>
> There is some discussion about tor in the related gnupg issue
>
>       https://dev.gnupg.org/T3348

thank you for the bug reference

> The documentation says
>
>     The default is to use Tor if it is available on startup or after
>     reloading dirmngr
>
> There is also "no-use-tor", but like disable-crl-checks there are
> security/privacy implications to using that.

i should have read the documentation before, now I understand: thanks!

in my case, there is no doubt the S/MIME signature verification was
stuck because Tor was stuck, when I restarted Tor all was fine again

Happy hacking! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2022-06-07 13:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 11:01 [bug?] emacs interface - some mark read tag changes may have failed Giovanni Biscuolo
2022-06-06 12:12 ` David Bremner
2022-06-06 13:18   ` Giovanni Biscuolo
2022-06-06 13:57     ` David Bremner
2022-06-06 18:07       ` Giovanni Biscuolo
2022-06-07  9:57         ` David Bremner
2022-06-07 13:13           ` Giovanni Biscuolo [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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8735ggk45m.fsf@xelera.eu \
    --to=g@xelera.eu \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).