[lkml]   [2007]   [Jul]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Crypto API Weirdnesses

On Tue, 31 Jul 2007, Felipe Balbi wrote:

> On 7/31/07, Akinobu Mita <> 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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-07-31 15:45    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean