Install "Hardware Wallet" for Consortium Blockchain -- Protect Hyperleger Fabric...
summary
Claims that Hyperledger Fabric node private keys run and never leave an Intel SGX enclave, implemented by hijacking and modified Go crypto layer and a plugin BCCSP that redirects key generation and signing into the enclave. Prototype seals keys for durability, supports exporting encrypted key material to an HSM export for backup, and is tested on Fabric 1.2 with notes about 1.4 key reload. Limitations: SGX availability on cloud CPUs, no per-signature authentication, and rotation depends on Fabric CA/version.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 5:00Fabric BT CSP
- 11:25BCC SP
- 19:28Why we are launching this tool
- 24:12Do you have any questions
- 24:57Why cant we rotate the private key
- 25:37Key rotations
- 27:12Key reload
- 28:12CPU support
- 30:12CPU migration
- 31:22API interface
- 32:57Authentication mechanism
related talks
37mInstall "Hardware Wallet" for Consortium Blockchain -- Protect Hyperleger Fabric...
27mSecurity++: Hide Your Secrets via a Distributed Hardware Security Mod...
24mKeynote: Brian Behlendorf, Executive Director, Hyperledger Project
53mHyperledger Fabric: The Enterprise Blockchain Framework
21mKeynote: Introducing Hyperledger
35mCreating your First Smart Contract on Hyperledger Fabric!
32mSecure Container with SGX: Protecting Secret in Cloud Environment
09mCompany Pitches