On 7/2/2018 8:48 AM, Werner Koch wrote:
On Sat, 30 Jun 2018 21:26, johndoe65...@mail.com said:
How can I force dirmngr to use port "9150"?
So Tor ports are fixed. As Niibe-san already explained Dirmngr will
first try port 9050 and if it is not able to connect (ECONNREFUSED) it
will try port 9150. This is implemented for Dirmngr in Libassuan.
On Debian Stretch I tried to do the same thing:
$ dirmngr --version
dirmngr (GnuPG) 2.1.18
Tor browser for linux (7.5.6) downloaded from the torproject.org site.
On linux it works out of the box! :)
Which bring me to two possible causes:
1) Cygwin dirmngr can't be used in that way.
If I start "tor.exe" from the Tor Browser for windows bundle it works
like a charm because Tor then listen on port 9050.
So I don't thing this is the issue.
2) Regression in dirmngr between version 2.1.18 and 2.2.8.
It looks like the code that is responsible for falling back to port 9150
when port 5090 is not available is somehow failing.
I'm stuck here and would appriciate any help on finding a solution to
this issue.
If any one can test dirmngr 2.2.8 and Tor Browser for linux 7.5.6 and
can let me know how it goes?
beyond '-v' and '--debug-all' what can I do to furder troubleshoot?
--
John Doe
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
