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

Joachim Breitner nomeata at debian.org
Fri Feb 8 13:33:08 UTC 2008


Hi,

Am Freitag, den 08.02.2008, 14:16 +0100 schrieb Jonas Meurer:
> On 08/02/2008 Joachim Breitner wrote:
> > > > I also observed:
> > > > $ strings /sbin/cryptsetup |grep -i padlock
> > > > padlock-rng
> > > > padlock-aes
> > > > padlock-sha
> > > 
> > > 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
> > 
> > Ah, I see. But running gdb during initrd to find out which function by
> > gcrypt caused this will be hard. And I just tried to cryptsetup open a
> > loopback-file, without such an error.
> 
> The errors are obviously not produced by cryptsetup itself, but rather
> by some initramfs magic. that's the reason why they only appear at boot
> process, and not at invoking cryptdisks/cryptsetup manually.

I’m not sure about his. I am pretty sure the error messages came _after_
I entered the password the first time, but _before_ cryptsetup exits,
which I noticed when I entered the password wrong the first time, and
the second prompt came after the error messages.

I’ll make sure this observation is correct at the next boot.

Also, fgrepping the contents of my initramdisk for padlock, I only get:
./lib/modules/2.6.24-1-686/kernel/drivers/crypto/padlock-aes.ko.
./lib/modules/2.6.24-1-686/kernel/drivers/crypto/padlock-sha.ko.
./sbin/cryptsetup.
./usr/lib/libcrypto.so.0.9.8.

so no script is manually loading these.

> > > Ok, so i believe that this is rather an issue with the debian linux 2.6.24
> > > kernel, not with cryptsetup.
> > 
> > Should I reassign this bug then to the kernel package? Or gcrypt?
> 
> neither cryptsetup nor gcrypt seem to cause the issue. and the kernel
> team should not be blamed for adding some new modules to be shipped
> with the kernel image.
> in my eyes the real problem is whatever initramfs script tries to load
> the modules per default. maybe you should contact maximilian attems
> <maks at debian.org> or the kernel team as maintainers of initramfs-tools,
> they're usually quite responsive.
> 
> I've cc'ed debian-kernel at lists.debian.org in this mail.

Thanks,

Greetings,
Joachim
-- 
Joachim "nomeata" Breitner
Debian Developer
  nomeata at debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nomeata at joachim-breitner.de | http://people.debian.org/~nomeata
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20080208/ebf8b6aa/attachment.pgp 


More information about the Pkg-cryptsetup-devel mailing list