[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v3 8/9] cryptodisk: Fix cipher IV mode 'plain64' always being
From: |
Daniel Kiper |
Subject: |
Re: [PATCH v3 8/9] cryptodisk: Fix cipher IV mode 'plain64' always being set as 'plain' |
Date: |
Tue, 8 Sep 2020 15:42:50 +0200 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
On Mon, Sep 07, 2020 at 05:28:04PM +0200, Patrick Steinhardt wrote:
> From: Glenn Washburn <development@efficientek.com>
Could explain here why this patch is needed? I know why but I would like
to have this explicitly stated in the commit message.
Daniel
- Re: [PATCH v3 4/9] luks2: grub_cryptodisk_t->total_length is the max number of device native sectors, (continued)
[PATCH v3 5/9] luks2: Improve error reporting when decrypting/verifying key, Patrick Steinhardt, 2020/09/07
[PATCH v3 6/9] cryptodisk: Unregister cryptomount command when removing module, Patrick Steinhardt, 2020/09/07
[PATCH v3 7/9] cryptodisk: Fix incorrect calculation of start sector, Patrick Steinhardt, 2020/09/07
[PATCH v3 8/9] cryptodisk: Fix cipher IV mode 'plain64' always being set as 'plain', Patrick Steinhardt, 2020/09/07
- Re: [PATCH v3 8/9] cryptodisk: Fix cipher IV mode 'plain64' always being set as 'plain',
Daniel Kiper <=
[PATCH v3 9/9] cryptodisk: Properly handle non-512 byte sized sectors, Patrick Steinhardt, 2020/09/07
Re: [PATCH v3 0/9] Cryptodisk fixes for v2.06, Daniel Kiper, 2020/09/09
Re: [PATCH v3 0/9] Cryptodisk fixes for v2.06, Patrick Steinhardt, 2020/09/17
Re: [PATCH v3 0/9] Cryptodisk fixes for v2.06, Glenn Washburn, 2020/09/21