You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature would like to see added to OpenZFS
OPAL encryption is now supported by dm-crypt using LUKS headers which seems like an approach OpenZFS could adopt as well.
How will this feature improve OpenZFS?
Leveraging the HW-supported algorithms would work around the brittleness of OpenZFS' crypto implementations (GCC plugins, LLVM CFI, etc have "adverse effects" on it - #15911) and take the cryptographic operations out-of-line of CPU operations and the DMU itself (performance benefit). Platform-specific binary would be reduced to the interfaces to OPAL functions from the various ways compilers currently produce ICP crypto code to improve portability (presuming those platform-level interfaces are consistent).
Unless I misunderstand the proposal, it makes no sense. Opal provides a block device encryption, same as LUKS, working on a range of device blocks. ZFS implements encryption on higher logical level, and I don't see how could it use Opal for anything.
OPAL encryption covers ranges of blocks on the underlying device, which would encrypt the metadata along with the data past the parts needed to direct decryption of the rest of the VDEV in datasets configured for encryption. Dataset level encryption would require the DMU to tell the volume manager which ranges of device blocks to encrypt and then write txgs for that dataset into those allocations.
Describe the feature would like to see added to OpenZFS
OPAL encryption is now supported by dm-crypt using LUKS headers which seems like an approach OpenZFS could adopt as well.
How will this feature improve OpenZFS?
Leveraging the HW-supported algorithms would work around the brittleness of OpenZFS' crypto implementations (GCC plugins, LLVM CFI, etc have "adverse effects" on it - #15911) and take the cryptographic operations out-of-line of CPU operations and the DMU itself (performance benefit). Platform-specific binary would be reduced to the interfaces to OPAL functions from the various ways compilers currently produce ICP crypto code to improve portability (presuming those platform-level interfaces are consistent).
Additional context
https://www.phoronix.com/news/Cryptsetup-Lands-OPAL-Encrypt
The text was updated successfully, but these errors were encountered: