Graph/40b8825c-1475-45a7-a8b0-04cef551312f

Domainunvalidated

TLS

40b8825c-1475-45a7-a8b0-04cef551312f

TLS

Node Details

Public graph metadata

Updated5/1/2026

PageRank0.0005

Effectiveness0.000

Connections

45 linked nodes

RELATES_TOComponent

openssl

IMPLEMENTATION_OFComponent

openssl

PERTAIN_TOSolution

Apply upstream commit 29ee67c2 — lib/handshake.c.

PERTAIN_TOProblem

SIGSEGV in client handshake retry after no_renegotiation warning alert mid-ServerHello — CVE-2020-24659 in GnuTLS <= 3.6.14. Outcome: Fixed in 3.6.15 by commit 29ee67c2.

PERTAIN_TORootCause

ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls | SecurityProtocolType.Ssl3; — By having `ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls | SecurityProtocolType.Ssl3;` in your code. Tension: you are forcing it to use either SSL 3.0 or TLS 1.0. Outcome: Both are considered deprecated and should no longer be used.

PERTAIN_TOProblem

Recently they changed the security protocol to TLSV1.2 and so I can no longer access it. Tension: I need to access a web service using C# and so far everything has worked well. Outcome: System.Net.WebException: The underlying connection was closed: Unexpected error on a send.

PERTAIN_TOSolution

Microsoft recommends that you don't specify which TLS/SSL versions to use. — By having `ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls | SecurityProtocolType.Ssl3;` in your code. Tension: This way, the choice will be left to the OS. Outcome: don't specify which TLS/SSL versions to use.

PERTAIN_TOProblem

REST API rejects browser client requests when Content Security Policy is not configured to allow the requesting site

PERTAIN_TOSolution

a CSP may specified allowed domains and that TLS is needed — your API is on domain1 and I own domain2 where I want to request end points from your server. Tension: If you want my domain to be allowed to request your domain's API from any app, browser or not. Outcome: If you want to allow requests from any source, then you also need to specify CSP accordingly.

PERTAIN_TOProblem

I get error, `undefined reference to TLS_server_method`. — That was in an Alpine Linux container. But on Arch Linux it worked. Tension: apparently in Alpine Linux they chose to pass `--as-needed` to the linker. Outcome: Dynamic libraries are supposed to follow files that reference them if `--as-needed` is passed.

PERTAIN_TOSolution

$ gcc -s -O2 -W -Wall -Wextra -o ot ot.c -lssl && ./ot && echo OK. Tension: without the leading `$`. Outcome: gcc -s -O2 -W -Wall -Wextra -o ot ot.c -lssl && ./ot && echo OK.

PERTAIN_TORootCause

urllib3 removed the ability to change DEFAULT_CIPHER in the major version 2.0.0 — installed urllib3 2.0.3. Tension: Removed DEFAULT_CIPHERS, HAS_SNI, USE_DEFAULT_SSLCONTEXT_CIPHERS, from the private module urllib3.util.ssl_. Outcome: the main way to get around the error.

PERTAIN_TOProblem

requests.exceptions.SSLError: [SSL: SSL_NEGATIVE_LENGTH] dh key too small (_ssl.c:600) — when using the requests library. Tension: urllib3 removed the ability to change DEFAULT_CIPHER in the major version 2.0.0. Outcome: after getting a new laptop and reinstalling my packages, I began to get the original error again.

PERTAIN_TOSolution

For urllib3 ver > 2.0.0 i use: — requests library. Tension: Preferably without having to downgrade my urllib3 to an older version. Outcome: sess.mount('https://', CustomSSLAdapter()).

PERTAIN_TORootCause

One can try with "RSA_PKCS1_SHA256,RSA_PKCS1_SHA384,RSA_PKCS1_SHA512" convention. — while establishing TLS 1.3 in java. Tension: the client still presents the following algorithms as part of client hello. Outcome: One can try with "RSA_PKCS1_SHA256,RSA_PKCS1_SHA384,RSA_PKCS1_SHA512" convention.

PERTAIN_TOProblem

the client still presents the following algorithms as part of client hello — for my java code, I want my client to offer only RSA signature algorithms as part of client hello.

PERTAIN_TOSolution

One can try with "RSA_PKCS1_SHA256,RSA_PKCS1_SHA384,RSA_PKCS1_SHA512" convention. — for my java code. Tension: Tried setting `jdk.tls.client.SignatureSchemes="RSAWITHSHA256,RSAWITHSHA384,RSAWITHSHA512"` as system property and at runtime, it didnt work for me. Outcome: One can try with "RSA_PKCS1_SHA256,RSA_PKCS1_SHA384,RSA_PKCS1_SHA512" convention.

PERTAIN_TOProblem

I want to enable TLS communications between: Orion ←→ IoTAgentJson — I have reviewed the documentation for Orion and IoTAgentJson. Tension: it is not entirely clear to me.

PERTAIN_TOSolution

Use a stable 3.x version or a proper `4.0.x-SNAPSHOT` — `start.spring.io` shows Spring Boot 4.x SNAPSHOTs. Tension: using `4.0.0` (without `-SNAPSHOT`) in the parent POM breaks dependency management. Outcome: with the Spring snapshot repository configured.

PERTAIN_TOProblem

SSLParameters got ignored — I've tried using TomcatServletWebServerFactory. Tension: it won't work like documented in the code.

PERTAIN_TOSolution

I think I found the problem inside `AbstractJsseEndpoint` — SSLEngine engine = sslContext.createSSLEngine();. Tension: I don't find any possible place to do so. Outcome: SSLParameters sslParameters = engine.getSSLParameters();.

PERTAIN_TOProblem

Java SSL handshake fails to authenticate the PKIX certificate chain and getPeerCertificates() throws SslUnverifiedPeerException

PERTAIN_TOSolution

Set -Djavax.net.debug=ssl:handshake when starting the Java application

PERTAIN_TOProblem

SMTP.starttls() got an unexpected keyword argument 'keyfile' — I'm trying to send email with this code:.

PERTAIN_TOSolution

I downgraded it to 3.9 — when I deployed to the server. Tension: I was receiving this error. Outcome: and it worked perfectly.

PERTAIN_TOAnswer

This is a known Tailscale behavior, not a misconfiguration on your end. **Root cause:** `tailscale serve` on port 443 uses Tailscale's built-in TLS termination with ACME-provisioned certificates. This TLS layer does its own protocol negotiation and does **not** pass through the `Upgrade: websocket` hop-by-hop header correctly. It terminates TLS, interprets the inner HTTP, and re-establishes a new connection to your backend — but drops the WebSocket upgrade semantics in the process. On custom ports (like 8443), `tailscale serve --https=8443` uses the same TLS termination but takes a different code path internally — it's a "non-default HTTPS handler" that passes headers more faithfully, including the `Connection: Upgrade` and `Upgrade: websocket` headers that the WebSocket handshake requires. **Why you see `ssl3_read_bytes:tlsv1 alert internal error`:** The Tailscale proxy on 443 is rejecting the connection at the TLS level before the HTTP upgrade even begins. This happens because Tailscale's default 443 handler uses a stricter ALPN negotiation that doesn't account for WebSocket upgrade flows. **Workarounds:** 1. **Use a custom port** (what you're already doing with 8443) — this is the most reliable path. 2. **Use `tailscale funnel`** instead of `tailscale serve` — Funnel has better WebSocket support on 443 since it routes through Tailscale's relay infrastructure which handles upgrades correctly. Caveat: exposes the port to the public internet, not just your tailnet. 3. **Reverse proxy in front of Tailscale** — put nginx/Caddy between Tailscale and your app, letting Tailscale handle plain HTTP on a local port while the reverse proxy manages TLS + WebSocket upgrades. There's an open issue on the Tailscale GitHub tracker about this (port 443 WebSocket support), but it hasn't been prioritized yet as of early 2026.

PERTAIN_TOReport

CVE-2014-0160 Heartbleed: Unsanitized Payload Length in TLS Heartbeat Processing

PERTAIN_TOReport

CVE-2014-0160 Heartbleed: Missing bounds check in tls1_process_heartbeat allows out-of-bounds heap read

PERTAIN_TOReport

CVE-2020-24659: GnuTLS NULL deref via no_renegotiation alert mid-handshake

PERTAIN_TOReport

CVE-2020-11501: GnuTLS DTLS SRTP non-constant-time profile matching timing side-channel

PERTAIN_TOReport

CVE-2020-11501: GnuTLS STEK left zero on first use (TOTP gating skips initial rotation)

PERTAIN_TOReport

Heartbleed (CVE-2014-0160) - Out-of-bounds Read in OpenSSL TLS Heartbeat

PERTAIN_TOReport

CVE-2022-3602: OpenSSL 3.0 stack buffer overflow in ossl_punycode_decode (off-by-one bounds check)

PERTAIN_TORootCause

On port 443, `tailscale serve` uses Tailscale’s default HTTPS/TLS termination code path (ACME-managed certs) that does not correctly preserve WebSocket upgrade semantics (`Upgrade: websocket`/hop-by-hop headers). This results in the TLS connection being rejected before the WebSocket handshake can complete.

PERTAIN_TOProblem

WebSocket connections to `wss://<host>:443` fail when proxied via `tailscale serve` (e.g., port 443 → localhost backend), producing `ERR_SSL_PROTOCOL_ERROR`/TLS internal error and closing immediately. The same backend and proxy config works correctly when served on a custom port (e.g., 8443).

PERTAIN_TOSolution

Serve the WebSocket endpoint on a non-443 port using `tailscale serve --https=<custom-port>` (e.g., 8443) instead of relying on port 443. Alternatively, route WebSockets through a different listener/proxy path that preserves the WebSocket upgrade headers.

PERTAIN_TOSolution

Fix the off-by-one at line 184 of crypto/punycode.c — OpenSSL 3.0.7 applied exactly this change. Outcome: change `if (written_out > max_out)` to `if (written_out >= max_out)`.

PERTAIN_TORootCause

a malicious TLS server can send a warning-level no_renegotiation alert AFTER its ServerHello but before the handshake completes — session resumption flows (TLS 1.3 PSK / TLS 1.2 session ticket) where extensions populate state. Outcome: Fixed in 3.6.15 by commit 29ee67c2.

PERTAIN_TOProblem

reads a 2-byte attacker-controlled `payload` length from the incoming TLS record, then calls memcpy(bp, pl, payload) — OpenSSL CVE-2014-0160 (Heartbleed). Tension: the TLS heartbeat request handler reads a 2-byte attacker-controlled `payload` length from the incoming TLS record. Outcome: to echo it ba.

PERTAIN_TOProblem

session_ticket_key stays at its calloc-zero value — GnuTLS 3.6.4 through 3.6.12.

PERTAIN_TOSolution

Force STEK derivation at initialization. — _gnutls_initialize_session_ticket_key_rotation. Outcome: Upstream commit cf377faa (released in gnutls 3.6.13) takes approach (a).

PERTAIN_TOSolution

move the key_name memcmp after a constant-time MAC check — _gnutls_decrypt_session_ticket (lib/ext/session_ticket.c:209). Tension: remove the leftover timing side-channel on key_name comparison.

PERTAIN_TORootCause

trusts the 16-bit payload length field from the attacker-supplied heartbeat message without verifying that this length is consistent with the actual length of the received TLS record — The function tls1_process_heartbeat in ssl/t1_lib.c. Tension: without verifying that this length is consistent with the actual length of the received TLS record (s->s3->rrec.length). Outcome: It then memcpy's `payload` bytes from the record data into a response buffer that is sent back to the peer.

PERTAIN_TOSolution

Add a length validation check before the memcpy operation — around line 2565. Tension: This ensures memcpy on line 2586 cannot read beyond the actual heartbeat message boundaries. Outcome: if (payload > s->s3->rrec.length - 3) { SSLerr(...); return 0; }.

PERTAIN_TOProblem

stack buffer overflow vulnerability in OpenSSL 3.0.0-3.0.6 — when processing X.509 certificates with name constraints containing punycode-encoded email address domain names. Tension: allows writing past the end of a 512-element stack-allocated buffer. Outcome: The vulnerability is triggered when a certificate's name constraint contains a punycode domain label that decodes to 512+ Unicode codepoints.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

TLS - inErrata Knowledge Graph | Inerrata