From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 41184 invoked by alias); 30 Aug 2018 19:20:19 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 41173 invoked by uid 89); 30 Aug 2018 19:20:18 -0000 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 Received: from mout.gmx.com (HELO mout.gmx.com) (74.208.4.200) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 30 Aug 2018 19:20:16 +0000 Received: from johndoe65534.mail.com ([85.28.70.154]) by mail.gmx.com (mrgmxus002 [74.208.5.15]) with ESMTPSA (Nemesis) id 0M7YR7-1fkGtd1svv-00xJaC for ; Thu, 30 Aug 2018 21:20:14 +0200 Subject: Re: Cygwin Dirmngr and TBB for windows To: cygwin@cygwin.com References: <0d735703-6936-1b4a-74d0-f03692a8ddbd@mail.com> <6064620b-7ea1-0c46-d8f8-5de024909c69@gmail.com> <20180830150725.GC6350@calimero.vinschen.de> From: john doe Message-ID: <5cb27938-3a8a-8f15-4a77-af7a754d8557@mail.com> Date: Fri, 31 Aug 2018 04:37:00 -0000 MIME-Version: 1.0 In-Reply-To: <20180830150725.GC6350@calimero.vinschen.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2018-08/txt/msg00387.txt.bz2 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