HSMs in Plain Envelopes: A Code Signing Story
summary
Project needs immediate Windows trust for a public open source release so code signing certificate choice and hardware tokens matter. Certificate arrives on a USB token in a plain envelope, vendor names (SafeNet/Gemalto/Thales) and CA docs mismatch, and signing requires Windows signtool or workarounds. Practical fixes: use OpenSC and PKCS#11 to talk to tokens, fix timestamp server calls, prefer YubiKey attestation or cloud HSMs for distributed signing, and favor regular code‑sign certs after the June FIPS mandate.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:05Foreword
- 2:52Code Signing Journey
- 3:40Obtain a Code Signing Certificate
- 9:56Talking to the Token
- 11:41Sign With the Token (code sign certificate)
- 14:54Code Signing Ecosystem
- 17:44Requests and Wishes
related talks
24mHSM Advances Supporting quantum-safe PKI Automation
33mDemystify Modern Signing: Keys, Certs, and Envelopes
49mEverything about code signing and how not to use it
50mBuild code signing and crypto PKI tooling
27mNo Keys? No Problem: Why You Can Trust Sigstore Signatures
27mSecurity++: Hide Your Secrets via a Distributed Hardware Security Mod...
37mSecuring Data in the Quantum Era: From the Root of Trust to Protecting Ecosystems
43mShhh - Stop Sharing Secrets, a Secure Mindset for Embedded Development
