From: Milan Broz <gmazyland@gmail.com>
To: "U.Mutlu" <for-gmane@mutluit.com>, dm-crypt@saout.de
Subject: Re: [dm-crypt] plain: opening with a wrong password
Date: Sun, 08 Feb 2015 11:33:47 +0100 [thread overview]
Message-ID: <54D73B8B.9000905@gmail.com> (raw)
In-Reply-To: <mb7clc$mli$1@ger.gmane.org>
On 02/08/2015 11:09 AM, U.Mutlu wrote:
>> And now thy mistake with plain IV:
>>
>> # echo "password" | cryptsetup create -c aes-cbc-plain -s 256 x /dev/sdb
>> # blkid -p /dev/mapper/x
>> /dev/mapper/x: UUID="f46ba5d8-8c26-4589-ac09-cb0829f2804f" SEC_TYPE="ext2" VERSION="1.0" TYPE="ext3" USAGE="filesystem"
>>
>> # mount /dev/mapper/x /mnt/tst
>> mount: wrong fs type, bad option, bad superblock on /dev/mapper/x,
>> missing codepage or helper program, or other error
>> ...
>>
>> DO NOT use plain mode if you are not sure what you are doing. Really.
> But isn't it just saying that the mount cannot be done
> because something is wrong, ie. wrong/incomplete cipher param was given?
For this particular case, yes. But no idea what happen if you try to run fsck
or other tool.
> What happens if you repeat the whole with the correct params?
Depends if there were write IO to that wrongly mapped device and what
these writes destroyed.
The whole point of this exercise is to note that you must use and
remember correct parameters if using plain mode, not only password.
> And, should one not use "/dev/sdb1" etc. instead of "/dev/sdb"?
No. Partition table is optional and it is not used on this disk.
Milan
next prev parent reply other threads:[~2015-02-08 10:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 12:33 [dm-crypt] plain: opening with a wrong password U.Mutlu
2015-02-04 13:02 ` Quentin Lefebvre
2015-02-04 13:30 ` U.Mutlu
2015-02-05 11:54 ` Arno Wagner
2015-02-05 13:53 ` U.Mutlu
2015-02-05 14:04 ` U.Mutlu
2015-02-05 23:51 ` Arno Wagner
2015-02-06 14:01 ` dennis
2015-02-06 14:19 ` Michael
2015-02-06 14:47 ` U.Mutlu
2015-02-06 18:27 ` Arno Wagner
2015-02-07 17:27 ` dennis
2015-02-07 18:03 ` Heinz Diehl
2015-02-07 23:16 ` Matthias Schniedermeyer
2015-02-08 8:19 ` Heinz Diehl
2015-02-08 9:23 ` Arno Wagner
2015-02-08 9:55 ` Milan Broz
2015-02-08 10:09 ` U.Mutlu
2015-02-08 10:33 ` Milan Broz [this message]
2015-02-09 3:13 ` Arno Wagner
2015-02-08 3:07 ` Arno Wagner
2015-02-08 2:59 ` Arno Wagner
2015-02-06 14:04 ` U.Mutlu
2015-02-06 18:20 ` Arno Wagner
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=54D73B8B.9000905@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=for-gmane@mutluit.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.