Hi Jonas,
At testing your patch I realized that $tries in initramfs is not used
like it is in the normal initscript. Instead, the default cryptsetup
(with three tries) is invoked $tries times. So if you give tries=5 in
/etc/crypttab, you have 3*5=15 tries in the initramfs.
Ah. I think I
On 21/02/2008 Helmut Grohne wrote:
Hi Jonas,
No. Testing takes time and I want to do that in one chunk. Furthermore I
need to rewrite the patch first. The patch doesn't permit an infinite
number of retries by setting tries=0. I'll tell you when I'm finished.
I verified that the
Hi Jonas,
No. Testing takes time and I want to do that in one chunk. Furthermore I
need to rewrite the patch first. The patch doesn't permit an infinite
number of retries by setting tries=0. I'll tell you when I'm finished.
I verified that the attached patch works as expected.
I object
On Thu, Feb 21, 2008 at 02:05:58PM +0100, Helmut Grohne wrote:
+ tries=*)
+ if [ ${x#tries=} -ge 0 ]; then
+ crypttries=${x#tries=}
+ fi
+ ;;
Nitpick (protects against error messages
Hey Helmut,
On 21/02/2008 Helmut Grohne wrote:
No. Testing takes time and I want to do that in one chunk. Furthermore I
need to rewrite the patch first. The patch doesn't permit an infinite
number of retries by setting tries=0. I'll tell you when I'm finished.
I verified that the
On 21/02/2008 David Härdeman wrote:
On Thu, Feb 21, 2008 at 02:05:58PM +0100, Helmut Grohne wrote:
+tries=*)
+if [ ${x#tries=} -ge 0 ]; then
+crypttries=${x#tries=}
+fi
+;;
Nitpick
On 18/02/2008 Helmut Grohne wrote:
Helmut, did you test your patch in the meantime? I'll apply it as soon
as I have confirmation from you that it works.
No. Testing takes time and I want to do that in one chunk. Furthermore I
need to rewrite the patch first. The patch doesn't permit an
Hello Jonas,
On Mon, 18 Feb 2008, Jonas Meurer wrote:
Maybe I don't understand your request, as you talk about /etc/fstab,
which not used by cryptdisks and initramfs cryptroot script at all.
Let me try to be clearer.
The script:
/usr/share/initramfs-tools/cryptroot
adds entries to
This is already packaged (as libgmyth0 and gmyth-utils) on Christian Marillat's
multimedia
archive. I don't know why it's not in Debian yet -- perhaps a licensing issue?
--
Eric Cooper e c c @ c m u . e d u
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
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
On Sat, Feb 16, 2008 at 08:31:36PM +0100, Jonas Meurer wrote:
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
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
Hi,
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 email
system. Could someone at
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
20 matches
Mail list logo
