linux-kernel - Re: Crypto API Weirdnesses

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 31 Jul 2007 19:23:48 +0530 (IST)
From:	Satyam Sharma <satyam@...radead.org>
To:	Felipe Balbi <felipebalbi@...rs.sourceforge.net>
cc:	Akinobu Mita <akinobu.mita@...il.com>,
	linux-kernel@...r.kernel.org,
	Herbert Xu <herbert@...dor.apana.org.au>,
	linux-crypto@...r.kernel.org, dm-devel@...hat.com
Subject: Re: Crypto API Weirdnesses

Hi,

On Tue, 31 Jul 2007, Felipe Balbi wrote:

> On 7/31/07, Akinobu Mita <akinobu.mita@...il.com> wrote:
> > > > "Failed to setup dm-crypt key mapping.
> > > > Check kernel for support for the aes-cbc-essiv:sha256 cipher spec and
> > > > verify that /dev/hda4 contains at least 133 sectors.
> > > > Failed to read from key storage"
> > >
> > > Looks like a "cryptsetup" error message, not kernel's.
> >
> > I can't find CONFIG_DM_CRYPT in the .config.
> > Maybe cryptsetup needs it.
> 
> yeah... it was that... working ;-)

Ugh, you should at least be checking if you've built the kernel with the
same config options :-) Of course, if you did a simple "make oldconfig"
but still lost some config options, then that's definitely a regression...
(was that the case here, btw?)

> btw... why DM_CRYPT is below "Multi-Devices" menu and not in
> "Cryptographic Options"?

Well, DM_CRYPT /is/ a device-mapper target first. "Cryptographic options"
is for _actual_ crypto code, such as algorithm implementations etc. Users
such as encrypting file systems / IPsec / dm-crypt are better off at their
logical places, I'd say.

Satyam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/