link2xt 82924952fb feat: allow TLS connections with invalid certificate if the key is unchanged ...

This change weakens TLS checks.
Every time we make a successful TLS connection,
we remember public key hash from the certificate
in relation to the hostname.
If later we connect to the same hostname and the public key does not change,
we skip checking certificate chain.
This way we will still connect successfully
even if certificate expires or becomes invalid for another reason,
but keeps the key.

We always check that certificate corresponds to the hostname.
We also do this for certificates starting with _
where we allow self-signed certificates,
so self-signed certificates with mismatching domains are not allowed.
Previously we did not check this for domains starting with _.

2026-04-17 18:07:20 +00:00

..

tls

feat: allow TLS connections with invalid certificate if the key is unchanged

2026-04-17 18:07:20 +00:00

dns.rs

chore: fix clippy warnings

2026-03-25 19:53:10 +00:00

http.rs

feat: allow TLS connections with invalid certificate if the key is unchanged

2026-04-17 18:07:20 +00:00

proxy.rs

feat: allow TLS connections with invalid certificate if the key is unchanged

2026-04-17 18:07:20 +00:00

session.rs

feat: log the number of read/written bytes on IMAP stream read error (#6924)

2025-07-17 20:01:16 +00:00

tls.rs

feat: allow TLS connections with invalid certificate if the key is unchanged

2026-04-17 18:07:20 +00:00