linux-ext4 - [Bug 112631] Cannot open encrypted Luks filesystem. Cruptsetup error.

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <bug-112631-13602-jWRMrmdc4J@https.bugzilla.kernel.org/>
Date:	Tue, 23 Feb 2016 08:34:39 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 112631] Cannot open encrypted Luks filesystem. Cruptsetup
 error.

https://bugzilla.kernel.org/show_bug.cgi?id=112631

STRSHR <strasharo2000@...oo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |strasharo2000@...oo.com

--- Comment #15 from STRSHR <strasharo2000@...oo.com> ---
(In reply to da_audiophile from comment #10)
> Regarding comment #9, Arch Linux ships cryptsetup-1.7.0-1 and when used with
> 4.1.18-1 does not fix this problem.
> 
> Enter passphrase for /dev/md0: 
> Failed to setup dm-crypt key mapping for device /dev/md0.
> Check that kernel supports aes-xts-plain64 cipher (check syslog for more
> info).
> 
> uname -r
> 4.1.18-1-lts
> 
> pacman -Qs cryptsetup
> local/cryptsetup 1.7.0-1 (base)

Does cryptsetup-1.7.0-2 resolve your issue?

https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/cryptsetup&id=ea2c8f73c45aa239ed5f356a8ecd01aeba51ef1d

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html