Git Archive - Rock the Prototype - Softwareentwicklung & Prototyping

Compromised CA Keys, Revoked Certificates – How Do We Verify That Revocation Really Works

Sascha Block2026-11-02T17:49:45+01:00Categories: IT Security|Tags: Auditability, Browser Security, CA Bundle, Certificate Authorities, Certificate Authority, Certificate Chains, Certificate Forgery, Certificate Revocation, Certificate Revocation List, Certificate Transparency, Certificate Validation, Code Signing, Code Signing Certificates, Compromised CA Keys, Compromised Private Keys, CRL, Cryptographic Keys, Cryptographic Vulnerabilities, CT Logs, curl, Cybersecurity, CycloneDX, digital certificates, Digital Signatures, Digital sovereignty, Digital Trust, eMudhra, eMudhra Security Incident, Git, Git-native Evidence, HTTPS, Identity Spoofing, Intermediate CA, IT Security, JetBrains, Key Generation, MacOS, Malware, Man-in-the-Middle, MITM, OCSP, Open Source Security, PKI, Public Key Infrastructure, Reproducible Security Testing, Revocation, Root CA, Root Store, Rust, rustls, rustls-webpki, SBOM, Secure by Design, Security Evidence, Security-by-Design, Software Signatures, Software Supply Chain, Supply Chain Security, TLS, TLS certificates, TLS Trust Validation, Trust Anchor, Trust Store, webpki-roots, Website Impersonation, X.509, Zero Trust|

Compromised CA Keys, Revoked Certificates - How Do We Verify That Revocation Really Works - eMudhra Security Incident: Eight compromised CA keys raise a fairly fundamental question for many of us in October 2026: "What's the point of revoking a certificate if applications keep trusting it anyway?"

Git

Compromised CA Keys, Revoked Certificates – How Do We Verify That Revocation Really Works

GitHub

Cookies von Drittanbietern