From: Hugo <hugo@riseup.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] not a valid LUKS device
Date: Fri, 26 Apr 2013 13:54:55 -0300 [thread overview]
Message-ID: <517AB15F.6090201@riseup.net> (raw)
In-Reply-To: <20130426141405.GA3188@tansi.org>
On 04/26/2013 11:14 AM, Arno Wagner wrote:
>> What is your opinion on this?
>
> Well, it is difficult to see what this bug really does, but
> if it really overwrites the first sector, then the salts
> in the LUKS header are gone and there is no way to recover
> from that without a header backup.
Sure, as expected. I will reformat that so.. :(
>
> It seems Ubuntu still does not understand how to keep its
> fingers off existing LUKS partitions. I recommend you complain
> to them.
I am trying.. But as I understand, it is seen by them as low priority
and who is interested in things out of the mainstream should achieve by
themselves.
Thanks Arno!
>
> Arno
>
next prev parent reply other threads:[~2013-04-26 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 13:12 [dm-crypt] not a valid LUKS device Hugo
2013-04-26 14:14 ` Arno Wagner
2013-04-26 16:54 ` Hugo [this message]
2013-04-26 18:26 ` 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=517AB15F.6090201@riseup.net \
--to=hugo@riseup.net \
--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