public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin Dirmngr and TBB for windows
Date: Fri, 31 Aug 2018 16:47:00 -0000	[thread overview]
Message-ID: <20180831083421.GE6350@calimero.vinschen.de> (raw)
In-Reply-To: <5cb27938-3a8a-8f15-4a77-af7a754d8557@mail.com>

[-- Attachment #1: Type: text/plain, Size: 2679 bytes --]

On Aug 30 21:20, john doe wrote:
> On 8/30/2018 5:07 PM, Corinna Vinschen wrote:
> > On Aug 30 14:35, Marco Atzeri wrote:
> > > Am 30.08.2018 um 11:30 schrieb john doe:
> > > > 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?
> > > 
> > > 
> > > a Simple Test Case will help to verify the claim.
> > 
> > Full ACK.
> > 
> > > connect is not expected to return EPERM
> > > http://pubs.opengroup.org/onlinepubs/9699919799/functions/connect.html
> > 
> > Cygwin does not explicitely generate EPERM anywhere near
> > AF_INET/AF_INET6 code.  Nor does a Winsock error exist which
> > gets gonverted to EPERM.
> > 
> > The *only* way to generate EPERM is if an underlying Winsock function
> > returns an error code not handled by Cygwin.  I never encountered
> > that case, though.  Thus, a STC is highly appreciated.
> > 
> > 
> > Corinna
> > 
> 
> Thanks both for your answer and your willingness to look into this.
> 
> STC:
> 1)  Have Tor Browser for Windows up and running.
> 2)  Start dirmngr:
>   $ mkdir ${HOME}/try
>   $ dirmngr --homedir ${HOME}/try -vvv --debug-all --server --use-tor
>   -> KS_GET -- 0x6C6ACD6417B3ACB1

That's not a STC.  STC means a simple, self-contained piece of (ideally)
C code to reproduce the issue.  I simply don't have the time to hunt
down something in lots of foreign code.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

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

  reply	other threads:[~2018-08-31  8:35 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
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 [this message]
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=20180831083421.GE6350@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.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).