From: djaonline <djaonline@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Can't connect to tls v1.0 server after update
Date: Thu, 11 Apr 2024 07:23:06 +0200 [thread overview]
Message-ID: <20240411052306.F1F52214C1@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: 1808 bytes --]
New comment by djaonline on void-packages repository
https://github.com/void-linux/void-packages/issues/49793#issuecomment-2048947232
Comment:
@classabbyamp
>then why did the issue not talk about this in the first place?!
My fault. I thought mentioning would be enough. Anyway thank you for your involvement.
>Anyway, gnutls supports TLSv1, your issue is not TLSv1:
Admins say they didn't change anything. Windows cisco any connect works without an issue. NetworkManager-openconnect had been working too before the update.
And the last try:). The result of `gnutls-cli xxx`:
```
Resolving 'xxx:443'...
Connecting to 'xxx.xx.xx.xx:443'...
- Certificate type: X.509
- Got a certificate list of 2 certificates.
- Certificate[0] info:
- subject `CN=*.xxx', issuer `CN=AlphaSSL CA - SHA256 - G4,O=GlobalSign nv-sa,C=BE', serial 0x6ae640253db2cdb9a97bf8a0, RSA key 2048 bits, signed using RSA-SHA256, activated `2024-01-23 13:51:08 UTC', expires `2025-02-23 13:51:07 UTC', pin-sha256="7w+pWPzVv52jlYzzLtQykOuGeiiMjakjQ3j6dR5WWqM="
Public Key ID:
sha1:c588dc648e300da16345c0d7de2f0fe4fcd30834
sha256:ef0fa958fcd5bf9da3958cf32ed43290eb867a288c8da9234378fa751e565aa3
Public Key PIN:
pin-sha256:7w+pWPzVv52jlYzzLtQykOuGeiiMjakjQ3j6dR5WWqM=
- Certificate[1] info:
- subject `CN=AlphaSSL CA - SHA256 - G4,O=GlobalSign nv-sa,C=BE', issuer `CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE', serial 0x7d4d42a92b431d7e6453e7c19a8d5877, RSA key 2048 bits, signed using RSA-SHA256, activated `2022-10-12 03:49:43 UTC', expires `2027-10-12 00:00:00 UTC', pin-sha256="BbrVIhEYvvBL6FiyC7nzVKLLDU3GPYdqHWAfk0ev/80="
- Status: The certificate is trusted.
*** Fatal error: The encryption algorithm is not supported.
```
next prev parent reply other threads:[~2024-04-11 5:23 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 ` [ISSUE] [CLOSED] " leahneukirchen
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 [this message]
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=20240411052306.F1F52214C1@inbox.vuxu.org \
--to=djaonline@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).