Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
Re: OpenSSL wrong version number error when using in-flight wifi
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Jeffrey Walton via curl-users <curl-users_at_lists.haxx.se>
Date: Mon, 22 Jul 2024 05:21:40 -0400
On Mon, Jul 22, 2024 at 2:02 AM Rohan Ganapavarapu via curl-users <
curl-users_at_lists.haxx.se> wrote:
>
> Only happens with some sites. I am on an united flight using in-flight
wifi.
>
> curl --version
>
> curl 8.7.1 (x86_64-pc-linux-gnu) libcurl/8.7.1 OpenSSL/3.0.13 zlib/1.3.1
c-ares/1.28.1 libpsl/0.21.5 nghttp2/1.61.0
> Release-Date: 2024-03-27
> Protocols: dict file ftp ftps http https imap imaps ipfs ipns mqtt pop3
pop3s rtsp smtp smtps tftp
> Features: alt-svc AsynchDNS HSTS HTTP2 HTTPS-proxy IPv6 Largefile libz
NTLM PSL threadsafe TLS-SRP UnixSockets
>
> curl -v https://ollama.com
>
> * Host ollama.com:443 was resolved.
> * IPv6: (none)
> * IPv4: 34.120.132.20
> * Trying 34.120.132.20:443...
> * Connected to ollama.com (34.120.132.20) port 443
> * ALPN: curl offers h2,http/1.1
> * TLSv1.3 (OUT), TLS handshake, Client hello (1):
> * CAfile: /etc/ssl/certs/ca-certificates.crt
> * CApath: /etc/ssl/certs
> * OpenSSL/3.0.13: error:0A00010B:SSL routines::wrong version number
> * Closing connection
> curl: (35) OpenSSL/3.0.13: error:0A00010B:SSL routines::wrong version
number
This can sometimes happen when you receive a plain-text document in place
of using TLS protocol messages. Human readable characters take the place of
binary version numbers seen in TLS handshake messages.
Based on Gisle Vanem's analysis, you were probably redirected to a [plain
text] Captive Portal to pay for the in-flight Wifi service. Captive Portals
are covered under RFC 8952, 8908, 8910 and friends.
Jeff
Date: Mon, 22 Jul 2024 05:21:40 -0400
On Mon, Jul 22, 2024 at 2:02 AM Rohan Ganapavarapu via curl-users <
curl-users_at_lists.haxx.se> wrote:
>
> Only happens with some sites. I am on an united flight using in-flight
wifi.
>
> curl --version
>
> curl 8.7.1 (x86_64-pc-linux-gnu) libcurl/8.7.1 OpenSSL/3.0.13 zlib/1.3.1
c-ares/1.28.1 libpsl/0.21.5 nghttp2/1.61.0
> Release-Date: 2024-03-27
> Protocols: dict file ftp ftps http https imap imaps ipfs ipns mqtt pop3
pop3s rtsp smtp smtps tftp
> Features: alt-svc AsynchDNS HSTS HTTP2 HTTPS-proxy IPv6 Largefile libz
NTLM PSL threadsafe TLS-SRP UnixSockets
>
> curl -v https://ollama.com
>
> * Host ollama.com:443 was resolved.
> * IPv6: (none)
> * IPv4: 34.120.132.20
> * Trying 34.120.132.20:443...
> * Connected to ollama.com (34.120.132.20) port 443
> * ALPN: curl offers h2,http/1.1
> * TLSv1.3 (OUT), TLS handshake, Client hello (1):
> * CAfile: /etc/ssl/certs/ca-certificates.crt
> * CApath: /etc/ssl/certs
> * OpenSSL/3.0.13: error:0A00010B:SSL routines::wrong version number
> * Closing connection
> curl: (35) OpenSSL/3.0.13: error:0A00010B:SSL routines::wrong version
number
This can sometimes happen when you receive a plain-text document in place
of using TLS protocol messages. Human readable characters take the place of
binary version numbers seen in TLS handshake messages.
Based on Gisle Vanem's analysis, you were probably redirected to a [plain
text] Captive Portal to pay for the in-flight Wifi service. Captive Portals
are covered under RFC 8952, 8908, 8910 and friends.
Jeff
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2024-07-22