DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 71D5E3858D28
Message-ID: <ead45228-0449-4d5f-7546-b0d1e0c55ec2@tsoft.com>
Date: Mon, 8 May 2023 10:50:25 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101
 Thunderbird/102.10.1
Subject: Re: OpenSSL failure in Cygwin: SSL_set_tlsext_host_name returns 1
 (SSL_TLSEXT_ERR_ALERT_WARNING)
Content-Language: en-US
To: cygwin@cygwin.com
References: <b31136f2-3401-34a8-ba89-7528c906bcd3@tsoft.com>
 <87o7mun2m1.fsf@Rainer.invalid>
In-Reply-To: <87o7mun2m1.fsf@Rainer.invalid>
From: Yuri via Cygwin <cygwin@cygwin.com>
Reply-To: Yuri <yuri@rawbw.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

On 5/8/23 10:40, Achim Gratz via Cygwin wrote:
> The port might not be open in the standard configuration of the Windows
> firewall.  Maybe you can use either openssl or curl to check what
> happens when you are trying to connect.


It looks like this function is used incorrectly, and it actually 
succeeds in Cygwin (returns 1) and fails on Linux/BSD (returns 0).

The upstream needs to fix this first.

I managed to make the program to work by making this just a warning.


Yuri


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple