Just Buy the Printer: Resilience in Action
summary
Four days before a release, a code signing certificate is due to expire and CA/Browser Forum rules have changed how private keys must be stored, forcing two parallel tracks: rework key storage to meet hardware/VAULT requirements and renew organisational validation stalled by a fraud flag. A handsigned paper attestation is accepted but the office printer is broken so someone buys a printer to get signatures; certificate rotation finishes two days early with no outage. code signing certificate expiring in 4 days
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:02Resilience as a doing word
- 1:44Code signing certificate incident
- 3:08Immediate response and compliance
- 4:11Fraud checks and printer purchase
- 5:13Certificate renewal and culture
- 6:36Why surprises happen
- 7:39Learning from incidents
- 8:42Sharing incident stories
- 10:25Step zero for sharing stories
related talks
23mHSMs in Plain Envelopes: A Code Signing Story
01h 01mCory Doctorow -
07mEstablishing Digital Trust
23mELI5: Implementing Digital Certificates for a Post-Quantum World
27mScaling Trust: CLM Roadblocks on the Path to Post Quantum Resilience
29mKeys, Certs and Vault: From DevSecOps to Post-Quantum
20mTrust Agility in an Era of Transient Ties: Rethinking TLS...
15mOne App at a Time: DigiCert's Practical Playbook for the Post-Quantum Transition