** No longer affects: null
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/62751
Title:
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
To manage notifications about this bug go t
** Project changed: upstart => null
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://bugs.launchpad.net/bugs/62751
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
I have this problem after an upgrade from 9.04 to 9.10. With 9.04, the
boot was interrupted and resumed again after I entered the passphrase
After upgrade to 9.10, the passphrase prompt appears and immediately the
graphical login screen appears. I switch back with ALT+CTRL+F1, but no
keystrokes ar
Yes that helps.
Thank you for the explanation.
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://bugs.launchpad.net/bugs/62751
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
It's a long story that depends on how you define "random" and
"secure". And this is really the wrong forum for this question and
answer. But I'll give it a whack anyway. :-)
/dev/random never hands out more bits than it has entropy available.
(It collects entropy from the timings of keyboard in
I use 7.10 but i didn't know that urandom saves the random seed during
start, restart and shutdown.
Everywhere on the net there can be read that urandom is not as secure as
random is. but i am a bit confused now. how could it be that urandom is
not as secure as random if uradom just saves the entr
What version of Ubuntu are you using?
On mine (7.10 aka. Gutsy), /etc/init.d/urandom already propagates the
random seed across reboots in /var/lib/urandom/random-seed.
This should make /dev/urandom very safe to use, assuming that file
itself is never compromised.
--
Upstart doesn't activate luk
Patrick J. LoPresti and mish,
thank you both for the help.
indeed /dev/random is the problem. Like mish said i could use
/dev/urandom. I don't have /dev/hwrandom, so the urandom solution or the
script mentioned in the manpage of random is the one i need.
As a theoretically question, how can i us
** Changed in: cryptsetup (Ubuntu)
Status: Confirmed => Fix Released
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://bugs.launchpad.net/bugs/62751
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I think your problem is related to using /dev/random in your crypttab
swap /dev/sda4 /dev/random swap
/dev/random collects entropy from different parts of the system
(including mouse/touchpad usage). I'm not sure, but I suspect entropy
is not saved at shutdown, so entropy must be collected again
/dev/random blocks until it has enough entropy to guarantee
randomness. That is probably why wiggling the touchpad gets things
going again.
If you have /dev/hwrandom, you can use that... Otherwise, you can use
/dev/urandom to avoid blocking, but theoretically this could give up
some security (si
Well it seems that is is a problem with the encrypted swap.
i changed the lines in fstab and crypttab this way:
fstab:
/dev/mapper/swap noneswapsw 0 0
/dev/mapper/home /home ext3defaults0 0
crypttab:
swap /dev/sda4 /dev/random swap
home /de
I have to say that this bug is not completely solved.
Some problems still exist. this is what i experience.
Using gutsy, up-to-date as of 08.03.2008
Encrypted partitions: home and swap
Type of encryption: Luks
crypttab:
home /dev/sda3 none luks,retry=1,cipher=aes-lrw-benbi
swap /dev/sda4 /dev/
A problem still exists:
ubuntu-7.10-desktop-amd64
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://bugs.launchpad.net/bugs/62751
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Due to the lack of responses that anyone can still confirm that the
described problem still appears, and the recent feedback that an
unrelated issue has been solved (thanks faithful for reporting back), I
come to the conclusion that this bug has been fixed some time ago. I
cannot really reproduce i
Ok my problem is resolved. Recent updates solved it.
Thanks.
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://bugs.launchpad.net/bugs/62751
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bu
zak, I'm rejecting the loop-aes-utils subtask, because this bug clearly
isn't about that part. at least, it is not visible at in in the bugtrail
what would need fixing in the loop-aes-utils package. If you still have
the bug, please file a new bug. thanks
** Changed in: loop-aes-utils (Ubuntu)
need more input on this bug
** Changed in: cryptsetup (Ubuntu)
Status: Confirmed => Incomplete
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://bugs.launchpad.net/bugs/62751
You received this bug notification because you are a member of Ubuntu
Bugs, which is
faithful: Please check if you really have no /usr/bin/env. (which is in
coreutils). Your system seems to be broken in strange ways.
Gabriel: are you still experiencing this bug with current gutsy? I'm using
cryptsetup on several machines in several configuration, and had no problems
mentioned i
env exists as a magic built-in in the initramfs busybox
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://bugs.launchpad.net/bugs/62751
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs ma
** Changed in: cryptsetup (Ubuntu)
Assignee: Scott James Remnant (keybuk) => (unassigned)
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://bugs.launchpad.net/bugs/62751
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Well, when starting without the splash parameter, everything works fine,
too. I meant to say that I've done no changes to the cryptdisk.functions
that would matter for this issue ;)
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://bugs.launchpad.net/bugs/62751
You re
no it doesn't. You are reenabling password input in usplash, which isn't a good
idea with current usplash
(try switching virtual consoles when entering your password to find out why)
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://bugs.launchpad.net/bugs/62751
You
Reinhard, correct me if I'm wrong but isn't the init.d call to
cryptdisks.functions already in the rootfs instead of the initramfs?
I'm running gutsy, and this configuration works fine:
$ cat /etc/crypttab
croot32 /dev/sda11 noneluks,cipher=aes-cbc-essiv:sha256
chome32 /dev/sda1
faithful <[EMAIL PROTECTED]> writes:
> In Gutsty doesn't work for me the error I get is this:
> exec: 34: env: not found.
> I use luks with keyfiles so commented out this lines in
> /lib//cryptsetup/cryptdisks.functions:
> ## Always output to console
> #stdin=`readlink /proc/self/fd/0`
> #if [ "
In Gutsty doesn't work for me the error I get is this:
exec: 34: env: not found.
I use luks with keyfiles so commented out this lines in
/lib//cryptsetup/cryptdisks.functions:
## Always output to console
#stdin=`readlink /proc/self/fd/0`
#if [ "${stdin#/dev/null}" != "$stdin" ] && [ "$ON_VT" != "
I have to admit that I lost a bit track of this bugreport. In gutsy, I
don't have any problems mounting my LUKS volume. I see a lot of feisty
reports in this bugreport, which probably won't get fixed, please open
another bugreport with [feisty] in the subject.
Is anyone seen this problem in gutsy
Works ok in Gutsy for me. At least for non root volumes, as I don't have
cryptroot myself.
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://bugs.launchpad.net/bugs/62751
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug con
Additional issue with crytroot setup in initramfs.
Usplash exits as it should, and the password gets read from console.
However the password prompt is never displayed. To solve this I changed
line 210 (feisty) from:
$cryptcreate < /dev/console
to
$cryptcreate < /dev/console > /dev/console 2>&1
As this package is in the " universe " repository, is is unlikely it
will get any non-critical / non-security updates in any other versions
than Gutsy. If anyon can test this against Gusty Tribe 4, I think it
would help in determining if this bug can be closed.
There have been a number of updates
Let me know if I can help reproducing / testing this bug. I could test
this on most any Ubuntu version pretty quickly.
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://bugs.launchpad.net/bugs/62751
You received this bug notification because you are a member of Ubuntu
> can't enter symbols that need "two fingers", or at least you can't have a ~
> in your passphrase!
Could it be that you use a non US keyboard before the keymap is actually
initialize?
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://bugs.launchpad.net/bugs/62751
Y
hi!
tonight i installed the latest feisty and set up an encrypted root partition.
the enter passphrase dialog showed up but was interrupted by some USB kernel
messages. after pressing enter the enter passphrase dialog showed up again and
i entered my (correct) passphrase. i got a message that th
** Changed in: cryptsetup (Ubuntu)
Status: Fix Released => Confirmed
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://bugs.launchpad.net/bugs/62751
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
ok, adding vol_id does the trick.
i now installed feisty and there is no need to add vol_id anymore. but i
got another problem.
The boot-splash switches to console, where i can see "Starting Cryptodisks" (or
similar message) but it didn't go automaticaly to the next step, "Enter
Passphrase".
I
you must edit /etc/crypttab and add to last row: 'vol_id'
in previous version this was default, now you must explicit add it.
my crypttab:
[EMAIL PROTECTED]:~$ cat /etc/crypttab
#
crypt /dev/hda2 none vol_id
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://launc
A little further information. On my other (luks) system it works fine.
Anyone got ideas as to what might be the non-luks specific bug?
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://launchpad.net/bugs/62751
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
like mish, i have the same problems with 2:1.0.4+svn26-1ubuntu1~edgy1 on
edgy.
it totally broke my system. i couldn't mount the encrypted home-
partition.
i switched back to 1.0.3, but now i get this error, the password-promt
on boot is not shown anymore, except this error:
"enter passphrase: co
Don't know if it's related but the latest cryptsetup update in edgy
appears to have broken setting up my (non luks) partition. I have
usplash turned off, but have been unable to get a passphrase prompt. I
have tried manually putting in the fixes to
/lib/cryptsetup/cryptdisks.functions but have ha
Using feisty with cryptsetup 2:1.0.4+svn26-1ubuntu1 I still don't get a proper
password prompt. Usplash is terminated correctly but the console isn't
switched. If I switch it manually, I can't enter the password anymore. (I can
write but all I write is shown in plain text).
Which means I have to
today i spent a whole 10hours on updating from dapper to edgy. Most of
the time i spent while trying to debug the latest cryptsetup-package i
compiled from feisty sources - with the final conclusion that it
couldn't work on my installation because the patches suggested in this
bug rely on /usr/bin/
cryptsetup (2:1.0.4-8ubuntu2) feisty; urgency=low
.
* fix and improve initramfs hook: terminate usplash if running, since
adequate secure text input is not possible with usplash ATM
* usplash support: Terminate usplash before asking a password.
Closes https://bugs.launchpad.net/ubu
I 'fixed' (since stty -echo didn't work) the password echo problem using
this trick:
added echo -n -e "Enter password: \033[40;30m" before the
$CRYPTCMD $PARAMS create $dst $src ... line
and echo -n -e "\033[40;37m" after it
it sets the fore+background color to black/black using an ansi color
esc
I didn't bother with Marc's patch when I found a one-liner and I'm OK
without usplash.
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://launchpad.net/bugs/62751
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubunt
Did you try Marc Schiffbauer`s Patch
(https://launchpad.net/products/upstart/+bug/62751/comments/53)? Except
for the password being printed plain text to the console it seems to
work fine for LUKS volumes even with usplash.
Extending the patch to support other dm-crypt volumes is only a matter of
I did Edgy upgrade yesterday and run into the same problem with my /home
partition.
After some trial and error, "two line fix for Edgy" by John Leach &
maikischa worked for me: patch do_luks() and do_noluks() functions in
/lib/cryptsetup/cryptdisks.functions to read passphrase directly from
/dev/c
Ok, forget it. The patch is wrong and totally useless :(. Guess it was just
luck and bad testing, that the error didn`t occur afterwards.
The problem still remains!
Add usesplash_write "QUIT" below usplash_write "CLEAR" in function do_luks()
to force it. If such an early termination of usplash i
Ups, missed two quotation marks in the patch file. Another example of
one error fixing another error ;).
** Attachment added: "cryptdisk.functions usplash patch v1.1"
http://librarian.launchpad.net/5620771/cryptdisks.functions-usplash_patch
--
Upstart doesn't activate luks volumes (also non l
Hi,
when I tried Marc`s patch for edgy, I stumbled across a major security issue.
When usplash exits early (as it does for example on a fsck on my machine) the
entered password is echoed plain text on the console. So I think it`s not such
a good idea to attach to a console when usplash is runni
** Summary changed:
- Upstart doesn't activate luks volumes in cryptsetup
+ Upstart doesn't activate luks volumes (also non luks) in cryptsetup
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://launchpad.net/bugs/62751
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
50 matches
Mail list logo
