linux-kernel - dm-crypt patch in Linux 4.20.6 Commit e4efd3184d9a63a7923e5c62fa236254f03c6bf8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1uWvFLIArHW8L5PlgMMbXz1fok_GsLiCTltivAZWDl9rHLjihpxmIzakchb_s1Ad_S267Ia3FqRj-fgsrm-ROZZuGVBOlHB1lplVZswHzNE=@protonmail.com>
Date:   Fri, 08 Feb 2019 11:39:00 +0000
From:   23pieces <23pieces@...tonmail.com>
To:     "stable@...r.kernel.org" <stable@...r.kernel.org>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: dm-crypt patch in Linux 4.20.6 Commit e4efd3184d9a63a7923e5c62fa236254f03c6bf8

Hello everyone!

It seems since kernelversion 4.20.6 many people have problems mounting their encrypted rootfs while booting.

Trying to investigate i found this commit in 4.20.6:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/md/dm-crypt.c?id=e4efd3184d9a63a7923e5c62fa236254f03c6bf8

To clarify this issue also persists in 4.20.7 and isn't occuring in 4.20.5.

People having the problem often have something like the following config on their rootfs (including myself):
cryptsetup -v --type luks --cipher aes-xts-plain64 --key-size 512 --hash sha512 --iter-time 5000 --use-random --verify-passphrase luksFormat device

I was trying to investigate the code in the commit and playing around with the dmsetup commands mentioned.

Now on a running system with kernel 4.20.6 i get:

dmsetup create test --table "0 8 crypt aes-cbc-essiv:sha3-256 9c1185a5c5e9fc54612808977ee8f5b9e 0 /dev/sdc 0"      Works

dmsetup create test --table "0 8 crypt aes-cbc-essiv:sha512 9c1185a5c5e9fc54612808977ee8f5b9e 0 /dev/sdc 0"
device-mapper: reload ioctl on test  failed: Invalid argument
Command failed.

dmsetup create test --table "0 8 crypt aes-xts-plain-64:sha3-256 9c1185a5c5e9fc54612808977ee8f5b9e 0 /dev/sdc 0"
device-mapper: reload ioctl on test  failed: Invalid argument
Command failed.

dmsetup create test --table "0 8 crypt aes-xts-plain-64:sha512 9c1185a5c5e9fc54612808977ee8f5b9e 0 /dev/sdc 0"
device-mapper: reload ioctl on test  failed: Invalid argument
Command failed.

At boot people have the following error:
device-mapper: reload ioctl on  failed: Invalid argument
Failed to setup dm-crypt key mapping for device /dev/disk/by-uuid/UUID
Check that kernel supports aes-xts-plain-64 cipher (check syslog for more info)

I don't have a patch for this yet, just wanted to inform you.

Best regards
23pieces

Download attachment "publickey - 23pieces@...tonmail.com - 0xC6F1867B.asc" of type "application/pgp-keys" (1823 bytes)

Download attachment "signature.asc" of type "application/pgp-signature" (510 bytes)