From: Arno Wagner <arno@wagner.name>
To: "Michael Kjörling" <152cc69a347e@ewoof.net>
Cc: cryptsetup@lists.linux.dev
Subject: Re: Assistance required
Date: Wed, 1 Feb 2023 00:07:16 +0100 [thread overview]
Message-ID: <20230131230716.GA29665@tansi.org> (raw)
In-Reply-To: <d08a3c6e-aa13-4af8-88a1-7375e827f3e6@home.arpa>
On Tue, Jan 31, 2023 at 14:09:05 CET, Michael Kjörling wrote:
> On 31 Jan 2023 10:58 +0100, from sensei.of.darkness@gmail.com (Sascha Sander):
> > But unfornutaley I need to know the previous passphrase to add a new one.
> > Is there *any* possibility to access the data?
>
> Unfortunately, the general answer to this is no, there is not.
>
> If it was possible to access the data inside a LUKS container without
> knowing a valid passphrase for the container, then that would
> completely undermine the entire purpose of having full disk encryption
> in the first place; so anything like that would be a serious design
> flaw.
I second that. What you are trying to do would completely
negate the LUKS security model if it was possible.
Hence it is not.
Regards,
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
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
prev parent reply other threads:[~2023-01-31 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 9:58 Assistance required Sascha Sander
2023-01-31 13:09 ` Michael Kjörling
2023-01-31 23:07 ` Arno Wagner [this message]
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=20230131230716.GA29665@tansi.org \
--to=arno@wagner.name \
--cc=152cc69a347e@ewoof.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox