[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#392248: marked as done (partman-crypto: Fails to load modules for manual dm-crypt)



Your message dated Wed, 11 Oct 2006 21:35:12 +0200
with message-id <20061011193512.GB3890@dp.vpn.nusquama.org>
and subject line Bug#392248: partman-crypto: Fails to load modules for manual dm-crypt
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: partman-crypto
Severity: normal

Hello again,

I used manual partitioning, and created one large
dm-crypt partiton, and when I went to configure it I got

  An Error occured while configuring encrypted volumes

  The configuration has been aborted.

The log said

  Check kernel for support for the aes-cbc-essiv:sha256 cipher spec and
  verify that /dev/ide/host0/bus0/target0/lun0/part1 contains at least
  258 sectors.

========
What I did

expert
language
cd-rom
load all offered modules
no pcmcia
load choose-mirror and crypto-modules
skip network
detect disks
partition disks
manually edit
create partition table - msdos
create one big partition
use for encryption - dm-crypt, default options except for erase data - no
configure encrypted partitions
choose passphrase (a very weak one)
And an error is thrown.
=========

/var/run/partman-cryto/modules is then empty, and udebs only has
partman-crypto-dm (I don't know if that is unusual).

/lib/partman/ciphers/dm-crypt/aes/module was present and modprobing its
contents worked. I then touched all of the required files in
/var/run/... and the install proceeded. Unfortuanately I neglected to
check lsmod before modprobe, and so I can't confirm what happened, but I
would guess crypto_load_modules wasn't called.

James



--- End Message ---
--- Begin Message ---
Hi James,

On Tue, Oct 10, 2006 at 10:45:36PM +0100, James Westby wrote:
> I used manual partitioning, and created one large
> dm-crypt partiton, and when I went to configure it I got
> 
>   An Error occured while configuring encrypted volumes
> 
>   The configuration has been aborted.
> 
> The log said
> 
>   Check kernel for support for the aes-cbc-essiv:sha256 cipher spec and
>   verify that /dev/ide/host0/bus0/target0/lun0/part1 contains at least
>   258 sectors.
...
> /lib/partman/ciphers/dm-crypt/aes/module was present and modprobing its
> contents worked. I then touched all of the required files in
> /var/run/... and the install proceeded. Unfortuanately I neglected to
> check lsmod before modprobe, and so I can't confirm what happened, but I
> would guess crypto_load_modules wasn't called.

This sounds very similar to a problem (#390568) we fixed in
partman-crypto version 15. I just tested with todays (2006-10-11) daily
businesscard iso and could not reproduce the problem, so I suspect this
was indeed the cause of it. Closing as this should be fixed in 
current daily builds. Thanks for your bug report :-)

cheers,
Max

--- End Message ---

Reply to: