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=IZ7PvbC+9UPFS5vk jSfkndJZXtkQasZZ9oig0AxNV6wCn1LKHeH4n7Kt48BVRr9an+i707zW2/3RwQpe FwdfhX+FzcBbRpGADj9qRMAFTgwFgOlGp5jPBKz5xumOTljwJfVeh/C6N4hELfsG 1EZesFKfe3owTy/L4L1+W9VsdZY= 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=Ll9HBbf2XuUuG7h/sjAniO m7SXA=; b=A0RX+ZnIBP6dzML1pqtieOVzbraMlS6wxPWRkavVl6xaAe/Rpx9tAR YplunW1uHC7+/2fXi9Yf1MfXiU9f300ybiWIj8O7NCDbN7+JQW//6wkJ+eyZk0Mj 0540mGGwYHWD+Ts5Ll2hbNzkA53zbdrSAl/md63eu+duigMLJ8DRw= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=Browser, Hx-languages-length:998, H*Ad:D*mail.com, 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> From: john doe Message-ID: Date: Thu, 30 Aug 2018 11:30:23 +0200 MIME-Version: 1.0 In-Reply-To: <0d735703-6936-1b4a-74d0-f03692a8ddbd@mail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes 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