From: "Konstantin V. Gavrilenko" <k.gavrilenko@arhont.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] HELP, luksFormat over existing container
Date: Sat, 07 Jan 2012 10:57:08 -0000 (GMT) [thread overview]
Message-ID: <a07caa07-6ef4-41ed-b9e7-eecf6782ab23@dynomob> (raw)
In-Reply-To: <37321234-b10d-4d2c-b47c-e2c25c1a2733@dynomob>
Hello list,
I have a problem :(
by mistake, instead of luksOpen I executed lukFormat on the loop device with associated cryptofile.
even though the key is was the same, I have no backup of original luksHeader, so I assume i have no way of recovering the SALT.
I am pretty much in Acceptance that it is not possible to recover anything, but would like to get an external confirmation, advice.
p.s. surprised and disappointing that cryptsetup does not issue a warning when running luksFormat over luks preformatted container :(
thanks
kos
next parent reply other threads:[~2012-01-07 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <37321234-b10d-4d2c-b47c-e2c25c1a2733@dynomob>
2012-01-07 10:57 ` Konstantin V. Gavrilenko [this message]
2012-01-07 12:48 ` [dm-crypt] HELP, luksFormat over existing container Arno Wagner
2012-01-08 9:59 ` Konstantin V. Gavrilenko
2012-01-08 11:40 ` Arno Wagner
2012-01-08 13:23 ` Konstantin V. Gavrilenko
2012-01-08 17:18 ` 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=a07caa07-6ef4-41ed-b9e7-eecf6782ab23@dynomob \
--to=k.gavrilenko@arhont.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.