-
**Is your feature request related to a problem? Please describe.**
TLS 1.3 support is missing.
**Describe the solution you'd like**
Add TLS 1.3 support.
**Describe alternatives you've consider…
-
### Pitch
Currently Mastodon can't connect to instances that only accept TLS 1.3.
### Motivation
In the future websites will move to TLS 1.3 only and Mastodon would break then. I …
-
2024-09-29 05:03:07 ERROR cthulhu::net_proxy::proxy::net: Failed to establish TLS connection: received fatal alert: CertificateUnknown,URI:www.googleapis.com:443
at src\net_proxy\proxy\net.rs:27…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Does this enhancement require public documentation?
- [X] I have added an Acceptance Criteria item for adding …
-
* [ ] remove TLSv1.0 and TLSv1.1 as default supported protocols in the TLS configuration sections for for Beats.
* [ ] remove TLSv1.0 as a supported config option entirely, so that only TLSv1.1 could …
-
### Enhancement Proposal
Traefik supports TCP routes off the shelf, it would be good to get support in the charm via a new relation or the existing one
Extended documentation is available [here]…
-
## Describe the bug
The current hickory-dns (formerly trust-dns) package build does not support DNS-over-TLS (DoT) or DNS-over-HTTPS (DoH) when forwarding queries to an upstream nameserver that sup…
-
Is there a plan for supporting TLS within the binding ? I‘m looking for a solution for writing a value to the Kostal Enector with TLS on Port 802. The encryption is mandatory for that.
…
-
Are there any plans to make iglucentral.com accessible over https?
-
Note that I haven't confirmed that TLS v1.3 is unsupported in the most recent version but it was confirmed to not be supported in [April](https://github.com/prisma/prisma/discussions/23633#discussionc…