*** This bug is a duplicate of bug 110970 ***
https://bugs.launchpad.net/bugs/110970
** Branch linked: lp:ubuntu/karmic/cryptsetup
--
"Enter passphrase" for LUKS/cryptsetup breaks usplash
https://bugs.launchpad.net/bugs/139363
You received this bug notification because you are a member of Ub
*** This bug is a duplicate of bug 110970 ***
https://bugs.launchpad.net/bugs/110970
Marking this bug as a duplicate of bug 110970 so we can merge our
discussion with ubuntu-dev that already put some work on it too.
** This bug has been marked a duplicate of bug 110970
When mounting encryp
This bug was fixed in the package cryptsetup - 2:1.0.6-6ubuntu1
---
cryptsetup (2:1.0.6-6ubuntu1) intrepid; urgency=low
* drop almost all ubuntu specific changes from the cryptsetup package,
because they have been merged in debian. Thanks a lot!
* merge from debian, remaining
No, I propose this as solution for the bug, that the current patch for
this issue isn't working if there's a fsck before. I'd like to know,
whether you (evidently you know better all this usplash stuff than I)
concern this as possible solution or not.
Bug 55159 doesn't appear here. I tried your in
10111 : Would that be a solution for bug 55159 ? We should also be sure
that the password is not echoed in the console or anywhere in plain
text. Also I thought more about your proposition to add cryptsetup
prompt in initramfs instead of init.d and this can make sense since
filesystem is not necess
Where does this bug with fsck come from? Maybe the file the password is read
from (/dev/.initramfs/usplash_outfifo) isn't empty but filled with the output
of fsck? If so, why can't you just empty it before prompting for the password
and then reading it?
"cat" will block if (as it should be) ther
Yes, I've observed this bug here too. I'll try to integrate the script
into initramfs first unlock when I have some time.
--
"Enter passphrase" for LUKS/cryptsetup breaks usplash
https://bugs.launchpad.net/bugs/139363
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Yes, it's another issue which would need attention before we add
cryptsetup prompt to usplash. I don't think that adding current
cryptsetup init.d processes to initramfs is a acceptable solution,
cryptsetup should still be started from init.d at this stage and when it
is configured this way. Keepin
Is it right that the patch isn't working if there's a fsck running
before the cryptodisks are started? Cause then something seems to fill
the password input with some strange huge text, so the monitor is full
of stars. Without fsck running before, I have no problems with the
patched file.
--
"Ent
I have the same issue here. It's really disturbing as I already invested
some hours getting rid of all the other trouble, cryption caused
together with usplash. Maybe there's a way to do the crypt-stuff within
the initramfs too? Just as workaround untill there's a real solution.
** Changed in: cry
Yes, as described in bug 55159, cryptsetup password through usplash
works correctly in initramfs, but not when started through init.d.
--
"Enter passphrase" for LUKS/cryptsetup breaks usplash
https://bugs.launchpad.net/bugs/139363
You received this bug notification because you are a member of Ubu
Yeah, I based on it since they should have the same behavior.
Does it work properly from initramfs?
--
"Enter passphrase" for LUKS/cryptsetup breaks usplash
https://bugs.launchpad.net/bugs/139363
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
The patch looks good (almost identical as the "cryptroot") that runs
with initramfs when installed in encrypted LVM with the alternate CD.
However, due to the security reasons explained in bug 55159, it is still
not suitable for a upload into intrepid or hardy, at least until the
"clear password in
** Summary changed:
- [gutsy] "Enter passphrase" for LUKS/cryptsetup breaks usplash
+ "Enter passphrase" for LUKS/cryptsetup breaks usplash
--
"Enter passphrase" for LUKS/cryptsetup breaks usplash
https://bugs.launchpad.net/bugs/139363
You received this bug notification because you are a member
14 matches
Mail list logo
