On 2021-02-24 at 12:40 +0100, Erich Eckner wrote:
> Hi,
>
> thanks, again, just a minor typo:
>
> > --use-tor
> > --no-use-tor
> >
> >The option --use-tor switches Dirmngr and thus GnuPG into ``Tor
> >mode'' to route all net‐ work access via Tor (an anonymity network).
> >Certain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On Wed, 24 Feb 2021, Werner Koch wrote:
On Fri, 22 Jan 2021 20:59, Erich Eckner said:
Thank you for your time! For everyone to benefit from my problem, I'd like
to suggest to clarify in the documentation, that and how tor will be
I'll
On Fri, 22 Jan 2021 20:59, Erich Eckner said:
> Thank you for your time! For everyone to benefit from my problem, I'd like
> to suggest to clarify in the documentation, that and how tor will be
I'll change the option description to:
--use-tor
--no-use-tor
The option --use-tor switches
On 2021-01-22 at 18:05 +0100, Erich Eckner via Gnupg-users wrote:
>
> I was more wondering, why gpg decides to go into "tor mode" on box #2,
> when there is actually no tor installed or running. I'm totally happy to
> force non-tor mode via config file, but I'm also open to help find the
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 22 Jan 2021, Erich Eckner via Gnupg-users wrote:
I was more wondering, why gpg decides to go into "tor mode" on box #2, when
there is actually no tor installed or running. I'm totally happy to force
non-tor mode via config file, but I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
first: Maybe I should migrate this discussion to the bug tracker? But I'm
always somewhat hesitant to open new bugs, because I always assume, I'm
just too stupid to properly configure everything :-)
On Fri, 22 Jan 2021, Werner Koch wrote:
On Fri, 22 Jan 2021 13:24, Erich Eckner said:
> Box 1: tor (but no DNS endpoint exposed), named listening on 127.0.0.1:53
> (used by /etc/resolv.conf)
In Tor mode we use 8.8.8.8 as DNS Server unless you use
--nameserver ipaddr
In ``Tor mode'' Dirmngr uses a public resolver via Tor to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 22 Jan 2021, Werner Koch wrote:
On Thu, 21 Jan 2021 15:05, Erich Eckner said:
2021-01-21 14:41:32 dirmngr[3623955.6] DBG: dns: libdns initialized (tor mode)
2021-01-21 14:41:32 dirmngr[3623955.6] DBG: dns:
Your are using Tor for DNS
On Thu, 21 Jan 2021 15:05, Erich Eckner said:
> 2021-01-21 14:41:32 dirmngr[3623955.6] DBG: dns: libdns initialized (tor mode)
> 2021-01-21 14:41:32 dirmngr[3623955.6] DBG: dns:
Your are using Tor for DNS queries, that is the actual DNS server is
8.8.8.8. Tor mode is used if you are running the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 20 Jan 2021, Werner Koch wrote:
On Wed, 20 Jan 2021 14:46, Erich Eckner said:
is queried. This resolves to some old address (my DNS configuration
error), which serves the wrong content. Is it right, that this SRV record
should be
On Wed, 20 Jan 2021 14:46, Erich Eckner said:
> is queried. This resolves to some old address (my DNS configuration
> error), which serves the wrong content. Is it right, that this SRV record
> should be queried? Should I update it or remove it?
Yes, the SRV record is used if there is no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 20 Jan 2021, Werner Koch wrote:
On Tue, 19 Jan 2021 17:24, Erich Eckner said:
error in the subject when doing `gpg - --locate-external-keys
Many -v don't really help here because the actual task is done by the
dirmngr process.
On Tue, 19 Jan 2021 17:24, Erich Eckner said:
> error in the subject when doing `gpg - --locate-external-keys
Many -v don't really help here because the actual task is done by the
dirmngr process. Thus to debug this put
log-file /somewhere/dirmngr.log
verbose
debug ipc,network,dns
On 2021-01-19 at 17:24 +0100, Erich Eckner via Gnupg-users wrote:
> What can cause a "Connection closed in DNS" error? (Maybe the error
> message can be improved: Doesn't dns use udp by default, which is
> connectionless?)
I think it means dns.c returned DNS_ECONNFIN [1], which gets converted
On Tue, Jan 19, 2021 at 11:01 PM Erich Eckner via Gnupg-users
wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> I checked the manual, and there is even a non-permanent solution:
>
> - --export-filter keep-uid="mbox = ..."
>
> lets you filter the exported uids :-)
Cool :-) , I did
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 19 Jan 2021, Stefan Claas wrote:
On Tue, Jan 19, 2021 at 6:28 PM Stefan Claas
wrote:
On Tue, Jan 19, 2021 at 6:26 PM Erich Eckner via Gnupg-users
wrote:
Advanced method is set up, direct method is not. The key has multiple UIDs
(one
On Tue, Jan 19, 2021 at 6:28 PM Stefan Claas
wrote:
>
> On Tue, Jan 19, 2021 at 6:26 PM Erich Eckner via Gnupg-users
> wrote:
>
> > Advanced method is set up, direct method is not. The key has multiple UIDs
> > (one for each of my email addresses). Or did I do something wrong when
> > exporting
On Tue, Jan 19, 2021 at 6:26 PM Erich Eckner via Gnupg-users
wrote:
> Advanced method is set up, direct method is not. The key has multiple UIDs
> (one for each of my email addresses). Or did I do something wrong when
> exporting the key to the WKD? Should I have removed the other UIDs there?
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Stefan,
thanks for your answer.
On Tue, 19 Jan 2021, Stefan Claas wrote:
On Tue, Jan 19, 2021 at 5:24 PM Erich Eckner via Gnupg-users
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I'm playing around with my WKD setup
On Tue, Jan 19, 2021 at 5:24 PM Erich Eckner via Gnupg-users
wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi,
>
> I'm playing around with my WKD setup (guess, why) and encountered the
> error in the subject when doing `gpg - --locate-external-keys
> er...@eckner.net`.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I'm playing around with my WKD setup (guess, why) and encountered the
error in the subject when doing `gpg - --locate-external-keys
er...@eckner.net`. Retrieving via curl and the manually-constructed url
works fine, also I cannot find
21 matches
Mail list logo
