Re: [PATCH RESEND v3 01/10] crypto: Introduce option and structure for detached LUKS header

2024-01-11 Thread Yong Huang
On Thu, Jan 11, 2024 at 10:58 PM Daniel P. Berrangé wrote: > On Thu, Jan 11, 2024 at 03:35:10PM +0100, Markus Armbruster wrote: > > Hyman Huang writes: > > > > > Add the "header" option for the LUKS format. This field would be > > > used to identify the blockdev's position where a detachable LUK

Re: [PATCH RESEND v3 01/10] crypto: Introduce option and structure for detached LUKS header

2024-01-11 Thread Daniel P . Berrangé
On Thu, Jan 11, 2024 at 03:35:10PM +0100, Markus Armbruster wrote: > Hyman Huang writes: > > > Add the "header" option for the LUKS format. This field would be > > used to identify the blockdev's position where a detachable LUKS > > header is stored. > > > > In addition, introduce header field in

Re: [PATCH RESEND v3 01/10] crypto: Introduce option and structure for detached LUKS header

2024-01-11 Thread Markus Armbruster
Hyman Huang writes: > Add the "header" option for the LUKS format. This field would be > used to identify the blockdev's position where a detachable LUKS > header is stored. > > In addition, introduce header field in struct BlockCrypto > > Signed-off-by: Hyman Huang > Reviewed-by: Daniel P. Berr

[PATCH RESEND v3 01/10] crypto: Introduce option and structure for detached LUKS header

2023-12-24 Thread Hyman Huang
Add the "header" option for the LUKS format. This field would be used to identify the blockdev's position where a detachable LUKS header is stored. In addition, introduce header field in struct BlockCrypto Signed-off-by: Hyman Huang Reviewed-by: Daniel P. Berrangé Message-Id: <5b99f60c7317092a

[v3 01/10] crypto: Introduce option and structure for detached LUKS header

2023-12-24 Thread Hyman Huang
Add the "header" option for the LUKS format. This field would be used to identify the blockdev's position where a detachable LUKS header is stored. In addition, introduce header field in struct BlockCrypto Signed-off-by: Hyman Huang Reviewed-by: Daniel P. Berrangé Message-Id: <5b99f60c7317092a