From: Milan Broz <mbroz@redhat.com>
To: Warren Crossing <warren.crossing@mofokom.biz>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] LuksResume with key on partition
Date: Thu, 06 May 2010 15:43:01 +0200 [thread overview]
Message-ID: <4BE2C765.4060801@redhat.com> (raw)
In-Reply-To: <4BE2C380.6050009@mofokom.biz>
On 05/06/2010 03:26 PM, Warren Crossing wrote:
> Milan Broz wrote:
>> On 05/06/2010 11:54 AM, Warren Crossing wrote:
>>
>>> I am using cryptsetup 2:1.1.0-2.1 from debian
>>> I tried to get the cvs but cant dig cvs.saout.de (not even from saout.de ns)?????
>>
>> http://code.google.com/p/cryptsetup/
>> (where do you get that old cvs address?)
>
> From www.saout.de. - is this an old dead site?
No, but svn and project page is now on Google code site. There is lot of old information
on wiki seems (But IIRC link to cryptsetup page was updated. Strange.)
>> try 1.1.1-rc2 please and if it doesn't work, I need some reproducer
>> (I tried simple passphrase and it works here, I think I even used 1.1.0 for test)
>
> I don't have a spare disk handy (perhaps tonight I can try) - so I tried with loops, but it fails with
>
> "Device /dev/loop4 is not a valid LUKS device."
luksSuspend/Resume is supported on LUKS devices only, it will be never supported
for plain devices (there is no way how to verify the passphrase is correct,
it can lead to data corruption.)
Instead of
> cryptsetup -c aes-plain -h sha512 -b 2048 create test /dev/loop4 -d key
you have to use
cryptsetup luksFormat /dev/loop4 key
then
cryptsetup luksOpen /dev/loop4 -d key
Keep default cipher better, not sure why are you using known-IV vulnerable mode here...
Milan
next prev parent reply other threads:[~2010-05-06 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 8:24 [dm-crypt] LuksResume with key on partition Warren Crossing
2010-05-06 9:02 ` Milan Broz
2010-05-06 9:54 ` Warren Crossing
2010-05-06 10:02 ` Milan Broz
2010-05-06 13:26 ` Warren Crossing
2010-05-06 13:43 ` Milan Broz [this message]
2010-05-07 14:37 ` Warren Crossing
2010-05-07 18:00 ` Milan Broz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BE2C765.4060801@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=warren.crossing@mofokom.biz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox