public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: curl, libcurl{4, -devel, -doc}, mingw64-{x86_64, i686}-curl 7.86 (TEST)
Date: Thu, 03 Nov 2022 15:43:26 +0900	[thread overview]
Message-ID: <20221103154324.AB10.50F79699@gmail.com> (raw)
In-Reply-To: <Y2MjCqOFZ0PqdN2G@xps13>

On Wed, 2 Nov 2022 22:10:18 -0400, gs-cygwin.com <gs-cygwin.com@gluelogic.com>
Re: [ANNOUNCEMENT] Test: curl, libcurl{4, -devel, -doc}, mingw64-{x86_64, i686}-curl 7.86 (TEST)
> On Thu, Nov 03, 2022 at 10:38:13AM +0900, Lemures Lemniscati wrote:
> > I failed to get https://cygwin.com/index.html by curl:
> > 
> > ==========
> > $ uname -svrmo; cygcheck -c curl libcurl4 libgsasl18 ca-certificates; rm -f index.html; curl -O https://cygwin.com/index.html; ls -l index.html
> > CYGWIN_NT-10.0-22621 3.3.6-341.x86_64 2022-09-05 11:15 UTC x86_64 Cygwin
> > Cygwin Package Information
> > Package              Version         Status
> > ca-certificates      2022.2.54-3     OK
> > curl                 7.86.0-1        OK
> > libcurl4             7.86.0-1        OK
> > libgsasl18           2.2.0-1         OK
> >   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
> >                                  Dload  Upload   Total   Spent    Left  Speed
> >   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
> > curl: (60) SSL certificate problem: unable to get local issuer certificate
> > More details here: https://curl.se/docs/sslcerts.html
> > 
> > curl failed to verify the legitimacy of the server and therefore could not
> > establish a secure connection to it. To learn more about this situation and
> > how to fix it, please visit the web page mentioned above.
> > ls: cannot access 'index.html': No such file or directory
> > ==========
> > 
> > I don't know whether the result is expeced.
> > If so, is there any help?
> 
> Lem: did this work for you with an older version of curl?
> 
> Please use 'curl -v -O https://cygwin.com/index.html' and identify the
> server with which you are having trouble. There is more than one server.
> 
> Cheers, Glenn

I guess it could work in June 2022.
But reverting upto curl-7.81.0 doesn't improve the situation.

Lem

========
$ curl -V
curl 7.81.0 (x86_64-pc-cygwin) libcurl/7.81.0 OpenSSL/1.1.1s zlib/1.2.13 brotli/1.0.9 zstd/1.5.2 libidn2/2.3.4 libpsl/0.21.1 (+libidn2/2.3.1) libssh2/1.10.0 nghttp2/1.50.0 libgsasl/1.10.0 OpenLDAP/2.6.3
Release-Date: 2022-01-05
Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS brotli Debug gsasl GSS-API HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM NTLM_WB PSL SPNEGO SSL TLS-SRP TrackMemory UnixSockets zstd

$ curl -v -O https://cygwin.com/index.html
* STATE: INIT => CONNECT handle 0x80008eb28; line 1835 (connection #-5000)
* Added connection 0. The cache now contains 1 members
* STATE: CONNECT => RESOLVING handle 0x80008eb28; line 1881 (connection #0)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* family0 == v4, family1 == v6
*   Trying 8.43.85.97:443...
* STATE: RESOLVING => CONNECTING handle 0x80008eb28; line 1965 (connection #0)
* Connected to cygwin.com (8.43.85.97) port 443 (#0)
* STATE: CONNECTING => PROTOCONNECT handle 0x80008eb28; line 2028 (connection #0)
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/pki/tls/certs/ca-bundle.crt
*  CApath: none
* Didn't find Session ID in cache for host HTTPS://cygwin.com:443
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* STATE: PROTOCONNECT => PROTOCONNECTING handle 0x80008eb28; line 2048 (connection #0)
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [70 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [1023 bytes data]
* TLSv1.2 (OUT), TLS alert, unknown CA (560):
} [2 bytes data]
* SSL certificate problem: unable to get local issuer certificate
* multi_done: status: 60 prem: 1 done: 0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
* The cache now contains 0 members
* Closing connection 0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
========

  parent reply	other threads:[~2022-11-03  6:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 21:24 Cygwin curl Maintainer
2022-11-02 18:07 ` Achim Gratz
2022-11-03  1:38 ` Lemures Lemniscati
     [not found]   ` <Y2MjCqOFZ0PqdN2G@xps13>
2022-11-03  6:43     ` Lemures Lemniscati [this message]
2022-11-03  7:36   ` ASSI
2022-11-03 17:48     ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221103154324.AB10.50F79699@gmail.com \
    --to=lemures.lemniscati@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).