** Branch linked: lp:ubuntu/karmic/cryptsetup
--
fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
https://bugs.launchpad.net/bugs/91405
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
cryptsetup (2:1.0.4+svn29-1ubuntu2) gutsy; urgency=low
* modprobe dm-mod from cryptsetup.functions. (LP: #64625, #91405)
-- Reinhard Tartler [EMAIL PROTECTED] Tue, 29 May 2007 13:31:39
+0200
** Changed in: cryptsetup (Ubuntu)
Status: Needs Info = Fix Released
--
fails to setup
I was wrong: sha1 didn't solved it really. I now have all modules loaded that i
need (new ones loop, cbc and blkcipher) were missing and now it works one day
and the other day not.
Seems to me like some kind of race condition between loading the modules and
crytosetups try to open the device.
I can confirm that modprobe sha1 fixed the problem for me on feisty.
However, my problem was that I couldn't *add* a key with luksAddKey -
the luksFormat worked fine
--
fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
https://bugs.launchpad.net/bugs/91405
You received this
Further to above, creating the device with --hash sha256 works too - a
variant on the above problem. Curiously, a luksDump still shows Hash
spec: sha1 though I don't know if it's related.
--
fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
For me, loading the module sha1 solved the problem completely.
Maybe anyone else can confirm that
--
fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
https://bugs.launchpad.net/bugs/91405
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
OK, this is a usability and lack of documetation problem.
You need to run **sudo** cryptsetup luksAddKey /dev/sdc3 and now it
works fine...
--
fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
https://bugs.launchpad.net/bugs/91405
You received this bug notification because
Just had to reinstall feisty. Used a herd 5 CD and installed cryptsetup.
Had a similar problem directly after installing cryptsetup but now after
loading the modules listed above it's gone. But i am pretty sure that i
had the modules loaded in edgy as well as i said above. So i'd say
different bug
Addon:
[EMAIL PROTECTED]:/dev$ cryptsetup --version
cryptsetup-luks 1.0.5
--
fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
https://bugs.launchpad.net/bugs/91405
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Not sure if that is the same bug.
I currently run feisty (kernel 2.6.20-14) and try to setup dm-crypt /
LUKS
So far I did jitter my harddisk with sudo dd if=/dev/urandom of=/dev/hda
Then I did install cryptsetup -- sudo apt-get install cryptsetup
hashalot
Then I created a 160 GB partition:
I'm having the same problem in feisty.
What I did and the error message:
cryptsetup luksFormat /dev/sda2
WARNING!
Daten auf /dev/sda2 werden unwiderruflich überschrieben.
Are you sure? (Type uppercase yes): YES
Enter LUKS passphrase:
Verify passphrase:
Failed to setup dm-crypt key
CORRECTION OF THE ABOVE
*blush* My fault. in feisty I don't have any errors anymore, I just thought
it was an error, but everything works fine (uhm, I used the wrong partition...)
I guess I thought it was an error because actually I _did_ have that
external disk error yesterday, but it's
I switched to feisty now and the problem is gone. (same crypted drive
etc) So it really seems to be edgy + the backport package.
--
fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
https://launchpad.net/bugs/91405
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
which is pretty surprising, since the feisty package and the one from
edgy-backports are built from exactly the same source. (only difference
is debian/changelog)
--
fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
https://launchpad.net/bugs/91405
--
ubuntu-bugs mailing
Does anyone know if this problem also affects feisty? Or Debian etch?
The backport works fine here. I upgraded because I was unable to enter a
passphrase on boot with the version in edgy. This issue was solved with
the backport.
Anyway... I wonder why people upgrading to a backport when the
Maybe that's a stupid question, but which log files am I supposed to
have a look on?
My crypt partition is mapped and mounted at bootup, but I can't find any
detailed information in dmesg, syslog, or /var/log/boot on what happens
whatsoever.
--
fails to setup dm-crypt key mapping.
** Summary changed:
- can't open crypted device using a keyfile (2:1.0.4+svn26-1ubuntu1~edgy1)
+ fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
--
fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
https://launchpad.net/bugs/91405
--
ubuntu-bugs mailing
17 matches
Mail list logo
