X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=b6FMh+QnXlRHxsjR
	9hp4DcsJw6ibHAeB9H/LD+2AAUliaAA6pnGMU3CpPt9nG0ma5aiollHDdIdPb9sO
	IJR+5VXQUm8Zn1CwFzmXm+sufJ/OwH+FGg+JEXOKwqX3n80C1OiP6o/wbNb69cEv
	tz/VThbLIqnYXpANryo3SP2KMdw=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=zy7tHtvhu30YdJL5oplLsd
	S2jnk=; b=WSGfRICELSkH/7/AepUOVXqmIKxF0IwvSRag+/WyAVx/LfKH/bpp/4
	Gji3nQ8oNd92gU5pfsIATNV6SPDk11K2mQXCdFzsF8Dl8gnB5y5eR8CdlzVlRmE9
	XP6eszlaIStPxV27MZiDa99jzI/4A8XI3ROrGOQmyX+hYgCPRmVpI=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-2.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=informations, claim, highly, HContent-Transfer-Encoding:8bit
X-HELO:	mout.gmx.com
Subject:	Re: Cygwin Dirmngr and TBB for windows
To:	cygwin AT cygwin DOT com
References:	<0d735703-6936-1b4a-74d0-f03692a8ddbd AT mail DOT com> <af86c6ad-0a31-d0b9-e8d9-e8f9371232a3 AT mail DOT com> <6064620b-7ea1-0c46-d8f8-5de024909c69 AT gmail DOT com> <20180830150725 DOT GC6350 AT calimero DOT vinschen DOT de>
From:	john doe <johndoe65534 AT mail DOT com>
Message-ID:	<5cb27938-3a8a-8f15-4a77-af7a754d8557@mail.com>
Date:	Thu, 30 Aug 2018 21:20:12 +0200
MIME-Version:	1.0
In-Reply-To:	<20180830150725.GC6350@calimero.vinschen.de>
X-IsSubscribed:	yes

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

Basically, dirmngr should be able to connect to TBB for Windows like it 
does on linux and retreave the key.

Let me know if more informations are needed.
I  came to this list  because the issue seems to come from Cygwin, 
according  to the discussion at the first URL in this e-mail.

-- 
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

- Raw text -