On Tue, Feb 24, 2009 at 07:28:34AM -, Martin Pitt wrote:
> I propose to set the original bug to "wontfix" in Intrepid then, at
> least until we found a rock solid solution in Jaunty. Or decide to
> entirely drop support for non-LUKS partitions.
I believe using 'udevadm settle' in place of the
Kees Cook [2009-01-28 19:01 -]:
> Sorry, I didn't think my opinion counted on this one since I uploaded it
> originally.
Well, if you make sure that you use the actual intrepid-proposed
package, as opposed to a local build, that's ok.
Thanks!
--
[regression] cryptsetup does not work on raw
Hi Kees,
Kees Cook [2008-10-31 21:45 -]:
> The diff in the description for bug 164044 shows the changes pretty well
> (i.e. replacing a single -e test with a loop using -e and vol_id). It
> is basically just a think-o when doing the copy/paste from local's
> version of this loop.
Ah, that ma
Kees Cook <[EMAIL PROTECTED]> writes:
> If there's still a race remaining, it would be solved by the time the
> user went to enter their password for the device.
For the passphrase case that would be indeed the ideal
solution. Problems with that approach:
- the user might use a keyfile on a rem
There was no device check loop/timeout in Hardy. Just a single udevsettle
and a -e test which would immediately fail if the device was missing.
The intrepid changes are certain much better, but the use of "vol_id"
is not valid.
The diff in the description for bug 164044 shows the changes pretty we
