Lines Matching full:hardware

12 Inline encryption hardware sits logically between memory and disk, and can
14 can control exactly how the inline encryption hardware will en/decrypt the data
18 Some inline encryption hardware accepts all encryption parameters including raw
20 hardware instead has a fixed number of "keyslots" and requires that the key,
24 Note that inline encryption hardware is very different from traditional crypto
27 hardware operates on I/O requests.  Thus, inline encryption hardware needs to be
30 Inline encryption hardware is also very different from "self-encrypting drives",
33 verify the correctness of the resulting ciphertext.  Inline encryption hardware
42 encryption hardware is absent.  We also want inline encryption to work with
44 the inline encryption hardware of the underlying devices if present, or else
56 - Different inline encryption hardware has different supported algorithms,
61 - Inline encryption hardware usually (but not always) requires that keys be
96 blk_crypto_profile serves as the way that drivers for inline encryption hardware
102 The blk_crypto_profile also manages the hardware's keyslots, when applicable.
136 filesystems) to be testable without real inline encryption hardware, and
169 without actual inline encryption hardware.  Second, similar to actual inline
170 encryption hardware, the crypto API doesn't accept keys directly in requests but
176 Note that regardless of whether real inline encryption hardware or
179 encryption hardware's implementation and the kernel crypto API's implementation
190 block_device -- either via hardware or via blk-crypto-fallback.  This function
241 hardware, e.g. how to program and evict keyslots.  Most drivers will need to
258 If there are situations where the inline encryption hardware loses the contents
278 At the time of this patch, there is no real hardware that supports both these
291 that it changes the on disk format depending on whether hardware inline
296 Because there isn't any real hardware yet, it seems prudent to assume that
297 hardware implementations might not implement both features together correctly,
299 kernel will pretend that the device does not support hardware inline encryption