From: Sebastian <r4p.t0x@googlemail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] No key available for this passphrase
Date: Fri, 25 Jan 2013 19:57:59 +0000 (UTC) [thread overview]
Message-ID: <loom.20130125T204809-958@post.gmane.org> (raw)
In-Reply-To: 20130125194011.GB23010@tansi.org
Arno Wagner <arno@...> writes:
> That is far too low. Your key-slot has been compromised.
> Have a look specifically at offset 0x10000, the problem seems
> to be only in the 512 bytes starting there.
>
> You can use option -v to get a hex-dump of that sector.
>
Well, it could have come to my mind to look at this address...
Offset 0x10000:
0000000 gpt LUKS�� ext4dev extended linux-swap(v1) linux-swap(new)
linux-swap(v0) linux-swap(old) hfs hfs+ ReIsEr4 LABELONE LVM2 _BHRfS_M
- The file system is damaged linux-swap ufs create new %1 file system udevsettle
udevsettle --timeout= udevadm settle --timeout= set partition type on %1 new
partition type: %1 using libparted shrink file system grow file system resize
file system delete partition Unable to find mount point ======================
libparted : ^(/[^ ]+) create empty partition path: %1 calW
How on earth did that end up here and what could have caused it? After this it
looks perfectly random again...
next prev parent reply other threads:[~2013-01-25 19:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 17:53 [dm-crypt] No key available for this passphrase Sebastian
2013-01-25 19:40 ` Arno Wagner
2013-01-25 19:57 ` Sebastian [this message]
2013-01-25 21:50 ` Arno Wagner
2013-01-26 10:15 ` Sebastian
2013-01-26 17:41 ` Arno Wagner
2013-01-27 8:42 ` Sebastian
2013-01-28 23:46 ` .. ink ..
2013-01-29 2:39 ` Arno Wagner
2013-01-31 13:43 ` Sebastian
2013-01-31 17:48 ` .. ink ..
-- strict thread matches above, loose matches on Subject: below --
2012-09-08 9:03 Marcos
2012-09-08 13:35 ` Arno Wagner
2012-09-08 18:47 ` Marcos
2012-09-08 20:02 ` Arno Wagner
2012-09-08 20:51 ` Marcos
2012-09-08 22:47 ` Arno Wagner
2012-09-09 12:53 ` Marcos
2012-09-09 13:49 ` Arno Wagner
2012-09-09 14:06 ` Marcos
2012-09-08 22:45 ` Matthias Schniedermeyer
2012-09-09 8:45 ` Milan Broz
2012-09-09 13:42 ` 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=loom.20130125T204809-958@post.gmane.org \
--to=r4p.t0x@googlemail.com \
--cc=dm-crypt@saout.de \
/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.