Github messages for voidlinux
 help / color / mirror / Atom feed
From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Can't connect to tls v1.0 server after update
Date: Wed, 10 Apr 2024 21:04:16 +0200	[thread overview]
Message-ID: <20240410190416.D79572431A@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49793@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

Closed issue by djaonline on void-packages repository

https://github.com/void-linux/void-packages/issues/49793

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.25_1 x86_64 GenuineIntel uptodate rFF

### Package(s) Affected

curl-8.7.1_1,gnutls-3.8.5_1, libcurl-8.7.1_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

`curl -v https://${someTLSv10server}` , where ${someTLSv10server} is a domain of tls v1.0 only supported server 
output: successful recieving of data

### Actual behaviour

`curl -v https://${someTLSv10server}` , where  ${someTLSv10server}  is a domain of tls v1.0 only supported server 
output:`...OpenSSL/3.1.5: error:0A000102:SSL routines::unsupported protocol`

### Steps to reproduce

`curl -v https://${someTLSv10server}` , where  ${someTLSv10server}  is a domain of tls v1.0 only supported server output:`...OpenSSL/3.1.5: error:0A000102:SSL routines::unsupported protocol`

  parent reply	other threads:[~2024-04-10 19:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 18:29 [ISSUE] " djaonline
2024-04-10 18:50 ` iFoundSilentHouse
2024-04-10 19:04 ` leahneukirchen [this message]
2024-04-10 19:04 ` leahneukirchen
2024-04-10 21:26 ` djaonline
2024-04-10 21:29 ` djaonline
2024-04-10 21:29 ` djaonline
2024-04-10 21:40 ` leahneukirchen
2024-04-10 21:49 ` classabbyamp
2024-04-10 22:49 ` djaonline
2024-04-10 22:56 ` djaonline
2024-04-11  0:09 ` classabbyamp
2024-04-11  5:23 ` djaonline
2024-04-11  5:23 ` djaonline

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=20240410190416.D79572431A@inbox.vuxu.org \
    --to=leahneukirchen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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 NNTP newsgroup(s).