public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: john doe <johndoe65534@mail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin Dirmngr and TBB for windows
Date: Thu, 30 Aug 2018 14:51:00 -0000	[thread overview]
Message-ID: <af86c6ad-0a31-d0b9-e8d9-e8f9371232a3@mail.com> (raw)
In-Reply-To: <0d735703-6936-1b4a-74d0-f03692a8ddbd@mail.com>

On 7/11/2018 10:11 AM, john doe wrote:
> Hi,
> 
> I'm trying to get Cygwin dirmngr to work with  Tor Browser for Windows.
> 
> Following some discussion on the gnupg user list it looks like that the 
> connect(2) function in Cygwin does not return the proper error code:
> 
> https://lists.gnupg.org/pipermail/gnupg-users/2018-July/060768.html
> 
> On the above link one of the dev suggest that connect(2) returns EPERMS 
> instead of ECONREFUSED.
> 
> If ECONREFUSED is not returned when port 9050 is queried the fallback 
> code in dirmngr will not be executed and port 9150 will never be used.
> 
> Using dirmngr on Debian with TBBfor linux works as expected.
> 
> Can anyone confirm that and subcequently make Cygwin return the proper 
> error code?
> 
> Any help is appriciated.
> 

As any one has been able to confirm that the issue is present in Cygwin 
code?
I didn't see anything regarding this issue in the beta version of Cygwin 
or did I mist it?

-- 
John Doe

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2018-08-30  9:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-11  8:11 john doe
2018-08-30 14:51 ` john doe [this message]
2018-08-30 15:07   ` Marco Atzeri
2018-08-30 23:41     ` Corinna Vinschen
2018-08-31  4:37       ` john doe
2018-08-31 16:47         ` Corinna Vinschen
2018-08-31 20:37           ` Brian Inglis

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

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

  git send-email \
    --in-reply-to=af86c6ad-0a31-d0b9-e8d9-e8f9371232a3@mail.com \
    --to=johndoe65534@mail.com \
    --cc=cygwin@cygwin.com \
    /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.
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).