[Pkg-cryptsetup-devel] Bug#464673: Bug#464673: cryptsetup seems to try to load some padlock modules

[Jonas Meurer]

On 08/02/2008 Joachim Breitner wrote:
> > > on my system, when cryptsetup starts the root crypto partition during
> > > the initrd phase, I get error messages that seem to come from modprobing
> > > padlock-* modules, although I do not have such a devices.
> > > 
> > > These messages are confusing, and I`m not really sure what to think of
> > > them, but they look too much like an error to me than they should.
> >
> > Could you provide the exact error message?
> 
> Not so easy, as it happens during the initramfs state.
>
> When I enter a wrong key, the error message (which seems to be just the
> result of a "modprobe padlock-something", no other output happening)
> appears before I can retry to enter the password again. This made me
> think that it’s a cryptsetup issue.

you could write the error down to a paper ;-)

does the message look like the following?
FATAL: Module padlock_rng not found.

> I also observed:
> $ strings /sbin/cryptsetup |grep -i padlock
> padlock-rng
> padlock-aes
> padlock-sha

you're correct, even though these strings don't come from cryptsetup.
searching for 'padlock' in the sourcecode of cryptsetup doesn't give any
results other than one comment in line 114 of utils.c:

/* Credits go to Michal's padlock patches for this alignment code */

the strings in /sbin/cryptsetup actually come from static linking
against libgcrypt:

$ strings /usr/lib/libgcrypt.a |grep -i padlock
padlock-rng
padlock-aes
padlock-sha

> > I doubt that this is an issue with cryptsetup. Sounds more like a
> > general problem with initramfs-tools. Does /etc/initramfs-tools/modules
> > contain any padlock-* modules?
> 
> No padlock does not appear anywhere in /etc.

same for me.

> > And did this happen forever, or was it introduced by some subsequent
> > package upgrade?
> 
> Oh, sorry for forgetting to mention that: It occurred after the upgrade
> to the kernel version 2.6.24.

Ok, so i believe that this is rather an issue with the debian linux 2.6.24
kernel, not with cryptsetup.

greetings,
 jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20080208/a6aa5a9c/attachment.pgp