Ignite: Monitoring and maintaining self-signed certificates is dangerous
summary
Argues self-signed certificates are unreliable for monitoring and shows a concrete internal CA in five minutes workflow: generate a long‑lived root key (example 16 years), create one or more intermediate certs, sign server CSRs, deploy three PEM files per server, and import the root into browser stores and regenerate caches. Recommends no CRL for simplicity, use SNI extension files, use strong passwords, and links an 8‑minute blog post with commands and scripts.
AI-written summary · about
related talks
36mYou Like It Or Not; You Need It! - PKI And Certificate Management
33mSo You Want to Run Your Own Sigstore: Recommendations for a Secure Setup
49mHerding Certs - How to Automate Certificate Management
42mLet's go HTTPS
31mPractical TLS Advice for Large Infrastructure
16mJust trust me - public key infrastructure in less than twelve minutes
20mTrust Agility in an Era of Transient Ties: Rethinking TLS...
13mBOSH & SSL Certificates - Rotating Certificates Smoothly