[Pkg-cryptsetup-devel] [clemens at endorphin.org: Re: possibly found a bug in Luks]

Jonas Meurer jonas at freesources.org
Sat Dec 22 02:01:26 UTC 2007


----- Forwarded message from Clemens Fruhwirth <clemens at endorphin.org> -----

Date: Fri, 21 Dec 2007 11:58:58 +0100
From: Clemens Fruhwirth <clemens at endorphin.org>
Subject: Re: possibly found a bug in Luks
To: Stefan Botzenhart <sb at basiszwo.com>,
	Jonas Meurer <jonas at freesources.org>

Hallo Stefan,

At Thu, 20 Dec 2007 22:19:51 +0100,
Stefan Botzenhart <sb at basiszwo.com> wrote:
> 
> Dear Clemens,
> 
> first I want to thank you for your great work with luks. It's a really 
> nice software.
> 
> To introduce myself in short:
> I am 25 years old, studying informatics at University of Karlsruhe and 
> working as a freelancer for a software company in Karlsruhe. There I'm 
> responsible for the linux (ubuntu) workstations. At the moment I realize 
> a new system setup which contains raid1 and full hard disk encryption. I 
> made it besides some challenges ;)
> 
> So that's enough ... let me explain the possible bug. The setup 
> mentioned above succeded with some handwork (updating grub and initramfs 
> because the installer doesn't do all the work for me (a line in 
> /etc/crypttab and one in /bott/grub/menu.lst were missing) )
>
> The bug: if there is no key in slot 0 then booting from harddisk fails 
> because the luks module in initramfs possibly needs this slot.
> If a key is present in slot 0, then everything is fine and my system 
> boots up.
> 
> Hopefully you can follow my description?! If you have any problems 
> understanding me do not hesitate to contact me!

Danke fuer deinen Bug Report. crypttab ist etwas Debian/Ubuntu
spezifisches. Grundsaetzlich sehr sinnvoll, und eventuell werde ich es
in die Hauptdistribution von LUKS einmal uebernehmen, aber derzeit
wende dich mit crypttab spezifischen Problem an die Debian/Ubuntu
Entwickler. Ich hab dir Jonas Meurer als Cc dieser Mail
gesetzt. Deinen Bug solltest du ausserdem auf
https://bugs.launchpad.net/ubuntu/ eintragen.

Grundsaetzlich zu key slots: cryptsetup luksOpen braucht natuerlich
einen key slot in dem ein aktiver key drin ist. Ob es 0 ist oder ein
anderer ist egal. Der return code von cryptsetup ist bei erfolgreichem
oeffnen immer 0.

Vielleicht koenntest du auch "booting from harddisk fails" naeher
beschreiben, am besten wiegesagt im Bug Tracker von Ubuntu.
---
Fruhwirth Clemens - http://clemens.endorphin.org 


----- End forwarded message -----



More information about the Pkg-cryptsetup-devel mailing list