On 7/5/2018 12:18 PM, john doe wrote:
On 7/4/2018 2:25 PM, Werner Koch wrote:
On Wed, 4 Jul 2018 09:11, gni...@fsij.org said:
The patch is: Don't try to look the error code, but fallback TOR_PORT2
always.
I don't like this patch because it is not specific enough.
If Cygwin really returns E
On 7/4/2018 2:25 PM, Werner Koch wrote:
On Wed, 4 Jul 2018 09:11, gni...@fsij.org said:
The patch is: Don't try to look the error code, but fallback TOR_PORT2
always.
I don't like this patch because it is not specific enough.
If Cygwin really returns EPERM, than this is a bug in the Cygwin
On Wednesday, July 4, 2018 2:25:41 PM CEST Werner Koch wrote:
> We should not try to fix bugs for Cygwin
> given that Cygwin is not offically supported.
I think that you have spent already way too much time with this thread. ;-)
IMO even a
#ifdef __CYGWIN__
# error No you don't
#endif
in a cen
On Wed, 4 Jul 2018 09:11, gni...@fsij.org said:
> The patch is: Don't try to look the error code, but fallback TOR_PORT2
> always.
I don't like this patch because it is not specific enough.
If Cygwin really returns EPERM, than this is a bug in the Cygwin
emulation because all Unix systems (and
On 7/4/2018 9:11 AM, NIIBE Yutaka wrote:
Hello,
john doe wrote:
I'm willing to confirm that but I'm not sure how I would do that!?
I am considering a patch like following. If you can build GnuPG for
Cygwin, you can try. Or, you can ask Cygwin's package maintainer for
GnuPG.
The patch is:
Hello,
john doe wrote:
> I'm willing to confirm that but I'm not sure how I would do that!?
I am considering a patch like following. If you can build GnuPG for
Cygwin, you can try. Or, you can ask Cygwin's package maintainer for
GnuPG.
The patch is: Don't try to look the error code, but fallb
On 7/4/2018 4:05 AM, NIIBE Yutaka wrote:
Werner Koch wrote:
... on Windows. Actually I developed the fallback on Windows becuase
there it is easier to install the Tor browser. Anyway, Gniibe probably
found and fixed the problem in our DNS resolver. I suggest to wait for
the next release - pr
Werner Koch wrote:
> ... on Windows. Actually I developed the fallback on Windows becuase
> there it is easier to install the Tor browser. Anyway, Gniibe probably
> found and fixed the problem in our DNS resolver. I suggest to wait for
> the next release - probably next week.
That's not for Cy
On Mon, 2 Jul 2018 20:46, johndoe65...@mail.com said:
> It looks like the code that is responsible for falling back to port
> 9150 when port 5090 is not available is somehow failing.
... on Windows. Actually I developed the fallback on Windows becuase
there it is easier to install the Tor brows
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 9
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 L
Hi Niibe,
On 6/29/2018 1:40 PM, NIIBE Yutaka wrote:
Hello,
Sorry, my explanation was not accurate. In the Tor-mode of dirmngr, it
uses the port 9050 at first. And there is some code to fallback to the
port 9150. It's like:
libdns_switch_port_p (gpg_error_t err)
{
if (tor_mo
On 6/29/2018 6:40 PM, john doe wrote:
On 6/29/2018 4:24 PM, Werner Koch wrote:
On Thu, 28 Jun 2018 17:05, johndoe65...@mail.com said:
dirmngr.conf:
use-tor
http-proxy socks5://localhost:9150
Nobody said that you should configure a proxy ;-)
Dirmngr has integrated Tor support which will be
On 6/29/2018 4:24 PM, Werner Koch wrote:
On Thu, 28 Jun 2018 17:05, johndoe65...@mail.com said:
dirmngr.conf:
use-tor
http-proxy socks5://localhost:9150
Nobody said that you should configure a proxy ;-)
Dirmngr has integrated Tor support which will be used automatically when
Tor or the Tor
On Thu, 28 Jun 2018 17:05, johndoe65...@mail.com said:
> dirmngr.conf:
>
> use-tor
> http-proxy socks5://localhost:9150
Nobody said that you should configure a proxy ;-)
Dirmngr has integrated Tor support which will be used automatically when
Tor or the Tor Browser is up and running. --use-tor
Hello.
Am Freitag, den 29.06.2018, 16:30 +0900 schrieb NIIBE Yutaka:
> john doe wrote:
> > Now, the next step is to configure dirmngr to do the same!:
> >
> > dirmngr.conf:
> >
> > use-tor
> > http-proxy socks5://localhost:9150
>
> Only "use-tor" is needed, then, dirmngr connects to localhost:
Hello,
Sorry, my explanation was not accurate. In the Tor-mode of dirmngr, it
uses the port 9050 at first. And there is some code to fallback to the
port 9150. It's like:
libdns_switch_port_p (gpg_error_t err)
{
if (tor_mode && gpg_err_code (err) == GPG_ERR_ECONNREFUSED
On 6/29/2018 9:30 AM, NIIBE Yutaka wrote:
john doe wrote:
Now, the next step is to configure dirmngr to do the same!:
dirmngr.conf:
use-tor
http-proxy socks5://localhost:9150
Only "use-tor" is needed, then, dirmngr connects to localhost:9150 for
Tor.
Looks like the issue isDNS name resol
john doe wrote:
> Now, the next step is to configure dirmngr to do the same!:
>
> dirmngr.conf:
>
> use-tor
> http-proxy socks5://localhost:9150
Only "use-tor" is needed, then, dirmngr connects to localhost:9150 for
Tor.
--
___
Gnupg-users mailing lis
On 6/28/2018 1:25 PM, Werner Koch wrote:
On Thu, 28 Jun 2018 11:54, johndoe65...@mail.com said:
Can you elaborate on how I would let "Cygwin dirmngr" use "Tor Browser
for Windows"?
I have not tested it but given that the Tor browser is listening on
localhost, TCP port 9150, I see no reason wh
On Thu, 28 Jun 2018 11:54, johndoe65...@mail.com said:
> Can you elaborate on how I would let "Cygwin dirmngr" use "Tor Browser
> for Windows"?
I have not tested it but given that the Tor browser is listening on
localhost, TCP port 9150, I see no reason why a native Windows Tor
Browser can't work
Hi Werner, thanks for your answer.
On 6/27/2018 6:51 PM, Werner Koch wrote:
On Mon, 25 Jun 2018 10:50, johndoe65...@mail.com said:
On Cygwin '/etc/resolv.conf' is not needed, as ilustrated by the
below log dirmngr requires 'resolv.conf':
Cygwin is Unix emulation on Windows and thus GnuPG co
On Mon, 25 Jun 2018 10:50, johndoe65...@mail.com said:
> On Cygwin '/etc/resolv.conf' is not needed, as ilustrated by the
> below log dirmngr requires 'resolv.conf':
Cygwin is Unix emulation on Windows and thus GnuPG considers the
platform to be unix. In turn /etc/resolv.conf is required.
> Co
Hi,
I'm using gpg2/dirmngr on Cygwin:
$ gpg2 --version
gpg (GnuPG) 2.2.8-unknown
libgcrypt 1.8.2
$ dirmngr --version
dirmngr (GnuPG) 2.2.8-unknown
On Cygwin '/etc/resolv.conf' is not needed, as ilustrated by the below
log dirmngr requires 'resolv.conf':
I used the commands from:
https://b
24 matches
Mail list logo
