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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=y2gZ7IlwX6ZwZXAlw9O+qTlI9SjCa670gauAMzckpe7kF2FL2Sb/4
	rc9PLkiML4nDGJdp/3uFIAz7TnWsWLmkxfXuVCgLN2XC1OGvt03vNd3+m39gyKYf
	TJZ1Br7J8v6JpPOlImZoRgQ4Xv/07h/xf32lNOkcvKl1GGKVCxxJvs=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=UDvGGSiyL+5Ndd4mvmi4RN/3KG0=; b=XQGQbTIeT/b9JPDltKez05gpZy51
	PCYL8HAeegoGBUpBpYBdhS0GMUqGya7Pnb4qDj6aiw0srVl/+2rlL771Sj4nYw1t
	kypVb7R15niYxzzo53gtVdT8SEjptd/9qxWwMxjsNjRZK5yo/C7/L7U5ZaavkC6u
	hrbxvxzGLJFE6Yg=
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=-99.5 required=5.0 tests=AWL,BAYES_40,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=30082018, 30.08.2018, EPERM, 9699919799
X-HELO: mout.kundenserver.de
Date: Thu, 30 Aug 2018 17:07:25 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin Dirmngr and TBB for windows
Message-ID: <20180830150725.GC6350@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-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>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="64LDleNqNegJ4g97"
Content-Disposition: inline
In-Reply-To: <6064620b-7ea1-0c46-d8f8-5de024909c69@gmail.com>
User-Agent: Mutt/1.9.2 (2017-12-15)

--64LDleNqNegJ4g97
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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,
> > >=20
> > > I'm trying to get Cygwin dirmngr to work with=C2=A0 Tor Browser for W=
indows.
> > >=20
> > > 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:
> > >=20
> > > https://lists.gnupg.org/pipermail/gnupg-users/2018-July/060768.html
> > >=20
> > > On the above link one of the dev suggest that connect(2) returns
> > > EPERMS instead of ECONREFUSED.
> > >=20
> > > 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.
> > >=20
> > > Using dirmngr on Debian with TBBfor linux works as expected.
> > >=20
> > > Can anyone confirm that and subcequently make Cygwin return the
> > > proper error code?
> > >=20
> > > Any help is appriciated.
> > >=20
> >=20
> > 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?
>=20
>=20
> 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=20
returns an error code not handled by Cygwin.  I never encountered
that case, though.  Thus, a STC is highly appreciated.


Corinna

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

--64LDleNqNegJ4g97
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAluICC0ACgkQ9TYGna5E
T6Bg7A/9EoxhcaouQN+CtepwybdG1mbpy6K5kn91WFbxAoDmd2+W/cDIbTRQFGMk
7+yE/cS3vJfXWxbX3gEfxKjtgoHNXn/57081rZXGJBhR9bnfROWBE4MD72IXjEFq
qL4GgZ89J387rY/xL92eVisCcNZHn2OSI7b5FXiaK7eopX1dvj/XBFRlSEhctyrk
v42/c0WmP+geG9zsippKhkaVSRvxCbjeaSo4OV4MyaW7DC7ltoTxiYkGQjlcD21D
S6EiKMr+Z7B+xUzbPGgqsfXlsK43swgl7yVKhmNvNZSsHLGP62+9sSVstDLv6mIL
iazgPy2k8wnyJpOSWTQsIJ2Uc9A3UypoGSv98sG6Jbp2UvbteamRMr6Jvr15EzWo
7ZwpSj1U+nbNG1K0DAsEKp4cjR7yZEVg1uJsDsgNQfMaZZgJEf9XDvQ2z3HnR2xx
vYfCVEqlPXYkeOAdyq7rhazeTJvrARO+8udiKNob/8xLcwmwLwRazFC5mr+PCmNR
3uZYyZ0kFIvb8pUsoeTeLBNsL+kOatQXmpJvdB488J+GqhxfeCNB80Im4cCU6SPX
MVJN7PVscKkBc+vdpaweI7qSAdrpeFIaf3J3DnbaShxVrgNBNruHtu88jSQIPQnr
mMu27MELZ7drmdlAX1wv7CXra+4WH3cmXFBNz9Dyi0gQWdlKmFY=
=KtPN
-----END PGP SIGNATURE-----

--64LDleNqNegJ4g97--