From: blobfish <blobfish@gmx.com>
To: cryptsetup@lists.linux.dev
Subject: Re: Looking for confirmation as I enter the acceptance stage.
Date: Mon, 24 Jul 2023 14:45:09 -0400 [thread overview]
Message-ID: <4817818.GXAFRqVoOG@laptop> (raw)
In-Reply-To: <31712b7d-402e-452b-9ebb-5ede7afd5186@home.arpa>
On Monday, July 24, 2023 2:17:28 PM EDT Michael Kjörling wrote:
>
> This doesn't _have_ to be a showstopper; it's possible that LUKS
> simply needs data that's outside of what you've sent, or maybe you've
> been using that file differently. (And please think thrice before
> sending more; remember, anyone who has a valid key slot passphrase to
> a header has access to the plain text data of the container if they
> can get their hands on the ciphertext data, and this mailing list _is_
> publicly archived. Absolutely do consider that key file compromised,
> possibly alongside your other, memorized passphrase for the
> container.) But it's somewhat of a downer.
>
> I would still say you have some chance when doing it with more data,
> though, so what I suggested previously is absolutely still worth
> trying. After all, the extraction I did left only 19823 bytes
> including the header signature at the start, which is plenty less than
> the canonical size of the full LUKS 1 header.
I assumed the key file was compromised as I sent it along with the mail. I am
a little disappointed about my passphrase as I have committed it to memory and
haven't used it for anything else. Oh well.
I have plans on getting another hard drive this afternoon and starting the
cloning process. 8TB drive, so going to take a while. After that I was going
to get back into your procedure. I will probably need some more hand holding,
so I will post back when all that is done.
Thanks.
next prev parent reply other threads:[~2023-07-24 18:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 22:40 Looking for confirmation as I enter the acceptance stage blobfish
2023-07-23 23:04 ` Michael Kjörling
2023-07-24 0:00 ` blobfish
2023-07-24 16:03 ` Michael Kjörling
2023-07-24 18:17 ` Michael Kjörling
2023-07-24 18:45 ` blobfish [this message]
2023-07-26 15:38 ` blobfish
2023-07-26 15:50 ` Michael Kjörling
2023-07-26 16:10 ` blobfish
2023-07-26 17:49 ` Michael Kjörling
2023-07-27 14:12 ` blobfish
2023-07-28 13:17 ` Michael Kjörling
2023-07-28 15:23 ` blobfish
2023-07-28 18:50 ` Looking for confirmation as I enter the acceptance stage. -- SOLVED Michael Kjörling
2023-07-29 12:58 ` blobfish
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=4817818.GXAFRqVoOG@laptop \
--to=blobfish@gmx.com \
--cc=cryptsetup@lists.linux.dev \
/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.