Enabling OCSP Stapling in OpenSSL TLS Servers
Learn how to enable OCSP stapling in an OpenSSL TLS server, see a minimal C callback example, and verify the stapled response with openssl s_client.
Loading…
ReadMeFeed / Community knowledge
#tls
Real questions. Useful conversations. Find the people who know your stack.
opensslTraefik ACME HTTP-01 Certificate Automation: Minimal Architecture Note
A minimal Traefik setup for automatic Let's Encrypt certificates using HTTP‑01 challenges, file storage, and HTTPS redirect.
traefikproxyDiagnosing OpenSSL TLS Handshake Failures: Symptoms, Checks, and Fixes
Learn how to recognize common OpenSSL TLS handshake failures, identify their likely causes, run ordered verification steps, apply targeted fixes, and know when to escalate.
Why does DBeaver fail to validate a PostgreSQL server's SSL certificate when the hostname resolves via DNS, and how can I configure a custom truststore to fix it?
When connecting to a PostgreSQL instance over TLS using DBeaver, the client sometimes rejects the server's certificate despite the certificate being valid and trusted by the system Java keystore. The issue appears to be related to DNS resolution of the host name used in the connection string, which may cause a mismatch between the certificate's subject alter
dbeaverHow can I diagnose DNS resolution and TLS certificate validation failures in Emacs when retrieving packages from HTTPS archives?
When Emacs attempts to fetch package archives over HTTPS using the built-in url library, it relies on system DNS resolution and GnuTLS for certificate validation. If either step fails, Emacs aborts the operation and reports a generic TLS error, making it hard to pinpoint whether the problem lies in name resolution or in the certificate chain. The goal is to
Algolia v4 JavaScript client strict TLS validation and custom CA bundle handling in Electron/React Native
Developers using Algolia's official JavaScript search client version 4 need to confirm whether the library honors custom certificate authority configurations when operating inside Electron or React Native wrappers. The v4 release enabled strict TLS verification by default and removed the previous fallback that tolerated self‑signed certificates, but the publ
electronAxios ignores NODE_TLS_REJECT_UNAUTHORIZED when a custom httpsAgent is provided
When using Axios with a custom httpsAgent , the library does not consult the NODE_TLS_REJECT_UNAUTHORIZED environment variable, causing certificate validation to behave as if rejectUnauthorized: true even when the variable is set to 0 . This behavior can lead to unexpected UNABLE_TO_VERIFY_LEAF_SIGNATURE errors in environments that rely on the variable to re
axiosWhat TypeScript configuration and typing practices prevent misinterpretation of DNS promise results during TLS certificate hostname validation?
When building TypeScript applications that validate TLS certificates by performing DNS lookups, developers rely on the dns and dnsPromises APIs to obtain A, AAAA, MX, or TXT records. The goal is to guarantee that the type definitions accurately reflect the shape of the resolved data so that certificate hostname validation logic can safely process the results
Reserved Subdomain TLS Certificate Renewal Uncertainty After ngrok 3.0 Configuration Changes
The goal is to clarify whether ngrok automatically renews TLS certificates for reserved subdomains without requiring manual intervention. Documentation for ngrok 3.x does not specify if background renewal occurs, and users have observed varying expiry dates in the dashboard, creating uncertainty about the reliability of reserved domains over time. Does ngrok
ngrok