Hi,
Ok, now I got the problem. You're correct, that the tries option doesn't
work for the cryptsetup version in debian/stable (2:1.0.4+svn26-1).
That's due to a mistake in upstream development. This has been fixed in
the cryptsetup package version 2:1.0.4+svn26-2, but unfortunately this
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
Hi,
sorry, forgot to actually attach the patch. here it is.
May I propose a different patch and try that instead?
greetings,
jonas
--- /usr/share/initramfs-tools/scripts/local-top/cryptroot2008-01-29
11:43:07.0 +0100
+++
On 16/02/2008 To Helmut Grohne wrote:
argh, you're right again. initramfs stuff doesn't support --tries yet.
Could you try the following patch against
/usr/share/initramfs//usr/share/initramfs-tools/scripts/local-top/cryptroot
regenerate your initramfs (update-initramfs -u) and see whether
On 16/02/2008 Helmut Grohne wrote:
Hi,
sorry, forgot to actually attach the patch. here it is.
May I propose a different patch and try that instead?
sure ;-)
The retry management basically happened below in the previous version:
Line 181:
count=0
while [ $count -lt 3]; do
reopen 430158
thanks
My problem was: a booting system asks only three times for a password
and then boots without the encrypted block device.
Your proposed solution was to set tries=0 in /etc/crypttab.
This does not increase the number of password questions at the boot
stage, so it does not
On 15/02/2008 Helmut Grohne wrote:
My problem was: a booting system asks only three times for a password
and then boots without the encrypted block device.
yes, that's the default. do you suggest to raise this default of three
tries? I object against this suggestion, especially for security
yes, that's the default. do you suggest to raise this default of three
tries? I object against this suggestion, especially for security
reasons.
I asked for a way to change it at all (without modifying files in /usr).
why don't you just raise the retries yourself in /etc/crypttab. As
On 06/02/2008 Helmut Grohne wrote:
This mail closes bug #430158 as the original submitter never replied to
any questions regaring it, and it doesn't really describe a bug.
I'm sorry I didn't receive [EMAIL PROTECTED] (and
maybe others). At least the mentioned message id did not enter my
9 matches
Mail list logo
