4 ms·
What would an actual secure workflow for signing artifacts look like? I'm thinking: Final round of "code review" by security engineer on high-security single-p
by ShredKazoo 4y ago
What would an actual secure workflow for signing artifacts look like?
I'm thinking: Final round of "code review" by security engineer on high-security single-purpose device, build artifact on that device, sign using hardware security module.
I put "code review" in scare quotes because code changes are potentially expensive at this point. For minor issues, turn to your standard workstation and file an issue for next release. For a major security problem, call off the release.
- throwawaaarrgh 4y agoOne guy named Jeff and his boss Clem have access to an offline PC with some signing software in a closet behind a badged door. Not TEMPEST secure unless they have govt contracts. For hardware stuff it might be at the factory.
- ShredKazoo 4y agoThanks, interesting. I don't see how TEMPEST is relevant?
- throwawaaarrgh 4y agoI mean, if you don't want state actors to steal your super secret keys, maybe secure the power lines and RFI
- ShredKazoo 4y agoI searched on Google for RFI, not sure what it stands for?
- wyldfire 4y agoI believe that RFI here is "RF interference." Here's links to learn more about the references above [1] [2]. [1] https://en.wikipedia.org/wiki/Tempest_(codename) https://en.wikipedia.org/wiki/Tempest_(codename) [2] https://en.wikipedia.org/wiki/Van_Eck_phreaking https://en.wikipedia.org/wiki/Van_Eck_phreaking
- throwawaaarrgh 4y agoYep. It is pretty trivial to extract encryption keys via either control of voltage or detection of electromagnetic radiation emanating from a server