Skip to main content

TLS

Browse all articles, tutorials, and guides about TLS

5posts

Guides

Posts

Linux
|10 min read

When the Clock Is Wrong: TLS, JWT and Signed-Request Failures From Clock Skew

A few minutes of clock skew can look like a broken certificate, bad credentials, or an authentication regression. Learn how time checks fail, how to inspect Linux time sync, and how to alert before an incident.

Security
|13 min read

eMudhra CA Compromise: Two Roots to Remove, and Dropping Comodo AAA Broke 1 of 16,125 Chains

Browsers blocked the compromised eMudhra TLS intermediates in hours, but images and runtimes read their own trust stores. We tested 34 stores, real curl, Python, Node.js and Go clients, and the chains that the top 20,000 sites send. Debian had to remove two roots because of a Sectigo cross-sign. Removing Comodo AAA broke 1 of 16,125 chains in our OpenSSL test.

Networking
|12 min read

Let's Encrypt Goes to 64-Day Certificates: When Does Your ACME Client Actually Renew?

Let's Encrypt moves to 64-day certificates on 10 February 2027, and its staging environment already issues them. We issued real 64-day staging certificates with certbot, acme.sh and lego and recorded when each one renews. The ARI clients renewed or scheduled their renewal around day 42. acme.sh 3.0.7 with --days 80 scheduled its renewal for day 79, 15 days after the certificate expired, and upgrading to 3.1.6 fixed that at the next check.

DevOps
|7 min read

node-postgres Silently Ignores Your TLS Config When the URL Says sslmode

If your connection string contains sslmode=require, the pg library throws away the ssl options object where you loaded your CA certificate, and verification fails with "self-signed certificate in certificate chain". Here is the trap, the fix, and the v9 changes coming.