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:to:from:subject:message-id:date:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=Aez
	DdEAmVkFnZGNoW1+PUdXN1bF4PfqENVwcuSZyf2k3YaQ05P/fkeAbA5M7w7fY4fU
	J9RUdFwY7fa/5FE0I6rS+sMkVNkqoVf/0pywngDh1KAQtIfQZvbA/jwe6945gQjv
	IbGu0IlKUoUQ8Fv25WbZtg3ZWKtNJS67FejBcvnU=
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:to:from:subject:message-id:date:mime-version
	:content-type:content-transfer-encoding; s=default; bh=mSc6pNAnW
	O06UkRD/mpeg53gIXY=; b=rw+6XD4HjzikQS17BHVQBgHQA9CXYRV0euYgZvL9f
	7o4WyoBL7+eQxDHyQZ+xLEpMvO3jheYrTf+ZZ3Ep6tVf+VUdq/F5I791wDkibmFx
	XYS+mUWr+VHVwXjZCgVHd1ZWAYXjSgQhC76cZjD+L0263GeamhnF9WwQq2wk1fyV
	tA=
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.2 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=H*F:D*mail.com, H*Ad:D*mail.com
X-HELO:	mout.gmx.com
To:	cygwin AT cygwin DOT com
From:	john doe <johndoe65534 AT mail DOT com>
Subject:	Cygwin Dirmngr and TBB for windows
Message-ID:	<0d735703-6936-1b4a-74d0-f03692a8ddbd@mail.com>
Date:	Wed, 11 Jul 2018 10:11:41 +0200
MIME-Version:	1.0
X-IsSubscribed:	yes

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.

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