** Branch linked: lp:~ubuntu-branches/ubuntu/intrepid/cryptsetup
/intrepid-proposed
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
** Branch linked: lp:ubuntu/karmic/cryptsetup
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
This bug was fixed in the package cryptsetup - 2:1.0.6-6ubuntu2.3
---
cryptsetup (2:1.0.6-6ubuntu2.3) intrepid-proposed; urgency=low
* debian/initramfs/cryptroot-script: we don't require vol_id to understand
the encrypted device, but we should check the device is fully up first
** Tags added: verification-done
** Tags removed: verification-needed
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
Steve,
I've tested the version in intrepid-proposed on the computer where the
cryptsetup package previously failed, and the new version works as
expected!
Thanks for looking into this!
Sven
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
Y
Sven, it would be particularly helpful if you could test this new
version of cryptsetup in intrepid-proposed, since you were reporting the
regression before. This new upload *should* enable cryptsetup on raw
encrypted drives while also working for crypted RAID devices.
--
[regression] cryptsetup
Accepted cryptsetup into intrepid-proposed; please test and give
feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed
for documentation how to enable and use -proposed. Thank you in advance!
** Changed in: cryptsetup (Ubuntu Intrepid)
Status: Confirmed => Fix Committed
A new revision of cryptsetup has been uploaded to jaunty that should
work for both use cases. Changelog:
cryptsetup (2:1.0.6-7ubuntu6) jaunty; urgency=low
* debian/initramfs/cryptroot-script: we don't require vol_id to understand
the encrypted device, but we should check the device is full
Thank you for quick testing, copied to -updates.
So with that we are now back to the original bug filed by Kees. I reset
the tags and bug status.
** Changed in: cryptsetup (Ubuntu Intrepid)
Status: Fix Released => Confirmed
** Tags removed: regression-update verification-done
--
[regres
This bug was fixed in the package cryptsetup - 2:1.0.6-6ubuntu2.2
---
cryptsetup (2:1.0.6-6ubuntu2.2) intrepid-proposed; urgency=low
* Revert previous update; this introduces a race condition when the
underlying device is a md device or similar, whose device node
appears bef
** Tags removed: verification-needed
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Hello,
I've upgraded cryptsetup to the version in intrepid-proposed and it has
indeed solved my problem. I can reboot now and it simply works :-)
Thank you all for the very quick solution!
Sven
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291
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
Sven, if you could test this new package in intrepid-proposed that would
be great (it should be available on archive.ubuntu.com in about 1.5
hours). Since this reverts the package to the exact state of intrepid
final, we can waive the 7 day maturing period here.
I propose to set the original bug t
This needs to be fixed in Jaunty then, too.
** Changed in: cryptsetup (Ubuntu Jaunty)
Assignee: (unassigned) => Kees Cook (kees)
Status: Fix Released => Confirmed
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this
Accepted into intrepid-proposed; please test and give feedback here.
Please see https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Thank you in advance!
** Changed in: cryptsetup (Ubuntu Intrepid)
Status: In Progress => Fix Committed
** Tags a
cryptsetup 1.0.6-6ubuntu2.2 uploaded. Martin/Colin, please review and
accept.
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
** Changed in: cryptsetup (Ubuntu Intrepid)
Status: Confirmed => In Progress
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Comments from Scott James Remnant, resident udev expert:
18:05 < Keybuk> device node can exist, but have no filesystem inside it,
because other things need to do magic
18:05 < Keybuk> e.g. md and devmapper devices
18:06 < Keybuk> the device node shows up when you create the name
18:06 < Keybuk> b
Sven,
Thanks for the follow-up. I'm reopening this bug and marking it as
'critical' since it appears to be a regression in a published update.
I believe the developer who prepared the update is away this week, but
we'll see what we can do about getting this resolved - if nothing else,
by reverti
Forgot to mention that / is one of the LVM logical volumes.
Sven
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
Hi,
My intrepid system was updated with cryptsetup 2:1.0.6-6ubuntu2.1 a
short while ago (via intrepid-updates).
Ever since, it will not boot with my encrypted root file system. It asks
for the password as usual, and when I enter it (correctly), it reports:
"cryptsetup: cryptsetup failed, bad pass
This bug was fixed in the package cryptsetup - 2:1.0.6-6ubuntu2.1
---
cryptsetup (2:1.0.6-6ubuntu2.1) intrepid-proposed; urgency=low
* debian/initramfs/cryptroot-script: do not require that vol_id
can parse the encrypted device as valid (LP: #291752).
-- Kees CookFri, 31 O
** Tags added: verification-done
** Tags removed: verification-needed
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
I've installed cryptsetup from intrepid-proposed on my laptop. The
system has been restarted and things are working as before.
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug notification because you are a member of Ubu
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
Sorry, I didn't think my opinion counted on this one since I uploaded it
originally. Yes, this works for me without problems. I will try to get
soren to comment.
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug notific
Kees, anyone, please test the version in -proposed. It has sat there for
three months, time to either pull it or verify it.
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug notification because you are a member of Ubuntu
intrepid-proposed package copied to jaunty.
** Changed in: cryptsetup (Ubuntu Jaunty)
Status: Triaged => Fix Released
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug notification because you are a member of Ubun
Accepted into intrepid-proposed, please test and give feedback here.
Please see https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Thank you in advance!
** Changed in: cryptsetup (Ubuntu Intrepid)
Status: Triaged => Fix Committed
Target:
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
** Changed in: cryptsetup (Ubuntu Intrepid)
Assignee: (unassigned) => Kees Cook (kees)
Status: Incomplete => New
Target: None => intrepid-updates
** Changed in: cryptsetup (Ubuntu Intrepid)
Importance: Undecided => Medium
Status: New => Triaged
** Changed in: cryptset
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
True that, I actually meant "ready" for a block layer level. But that
should be checked at a different place anyway.
Has this check been there in hardy?
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug notification beca
If there's still a race remaining, it would be solved by the time the
user went to enter their password for the device. I'm not sure there is
a better way to test that the device is ready since it can be a raw-
encrypted drive.
--
[regression] cryptsetup does not work on raw encrypted drives
htt
The vol_id call was introduced to parse LUKS data? I see that removing
it unbreaks raw devices, but doesn't vol_id also make sure that the
device is fully settled, as opposed to a RAID just being halfway up or
so? Or is that handled later?
You don't need to wait until Jaunty opens. We can upload t
Once jaunty opens, I can get the cryptsetup patch uploaded so the SRU
can move forward.
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Attached is the proposed fix.
** Attachment added: "cryptsetup_1.0.6-6ubuntu2.1.debdiff"
http://launchpadlibrarian.net/19143960/cryptsetup_1.0.6-6ubuntu2.1.debdiff
--
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug no
39 matches
Mail list logo
