From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] No key available for this passphrase
Date: Fri, 25 Jan 2013 22:50:43 +0100 [thread overview]
Message-ID: <20130125215043.GA23744@tansi.org> (raw)
In-Reply-To: <loom.20130125T204809-958@post.gmane.org>
On Fri, Jan 25, 2013 at 07:57:59PM +0000, Sebastian wrote:
> 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
Urks. Looks like a fragment from a menu or script?
> How on earth did that end up here and what could have caused it?
No idea.
> After this it looks perfectly random again...
As expected. The entropy-test is pretty sensitive.
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
next prev parent reply other threads:[~2013-01-25 21:50 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
2013-01-25 21:50 ` Arno Wagner [this message]
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=20130125215043.GA23744@tansi.org \
--to=arno@wagner.name \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox