[Pkg-cryptsetup-devel] Bug#430158: Bug#430158: closed by Jonas Meurer <jonas at freesources.org> (closing because of inactivity)

Jonas Meurer jonas at freesources.org
Sat Feb 16 17:33:03 UTC 2008

reopen 430158

On 16/02/2008 Helmut Grohne wrote:
> > As you can see, this bug has been fixed for a long time, so I'm closing
> > the bugreport again. Unfortunately, this will never make it into etch,
> > which is due to debians stable release policy. If you insist on this
> > feature, I could prepare a backport of the current cryptsetup package
> > version 2:1.0.6~pre1+svn46-1 for backports.org. What do you think about
> > that?
> I normally don't use etch, so could you be so kind to explain me how you
> fixed it? I really don't see this:
> My unstable system has 2:1.0.6~pre1+svn45-1, so this should have the fix
> included. The script for activating cryptsetup is the one mentioned
> above.
> On line 173 I can see:
> 	cryptcreate="/sbin/cryptsetup luksOpen $cryptsource $crypttarget"
> $cryptsource is tested for -e, so this will not include --tries and
> $crypttarget is similarly tested for -e /dev/mapper/$crypttarget, so
> this command does not include a --tries.
> Later in line 198 (I don't run a keyscript not bootsplash):
> 	$cryptcreate < /dev/console > /dev/console 2>&1
> The command is just verbatim executed, no --tries.
> The whole script doesn't even contain -T nor --tries, so how do the
> number of tries get into that script? I really don't see that, sorry.

argh, you're right again. initramfs stuff doesn't support --tries yet.
Could you try the following patch against
regenerate your initramfs (update-initramfs -u) and see whether this
works for you? I'm not quite sure that I added all necessary changes, so
a test by you would be helpful. Unfortunately I've no possibility to
test this quite now, so I would have to setup a test environment first.

thanks for being so persistent ;-)


More information about the Pkg-cryptsetup-devel mailing list