From: "Michael Kjörling" <michael@kjorling.se>
To: dm-crypt@saout.de
Subject: [dm-crypt] Re: reg: Question on LUKS device's content exposure
Date: Sun, 17 Oct 2021 10:20:05 +0000 [thread overview]
Message-ID: <cde99332-54c8-4341-92f0-02ab5d7b19da@localhost> (raw)
In-Reply-To: <20211016201541.GA18893@tansi.org>
On 16 Oct 2021 22:15 +0200, from arno@wagner.name (Arno Wagner):
> As to the idea with a dedicated, alerted rack, I know of real-world
> installations that do exectly that. This will fail with a competent
> attacker as well though, as physical locks and tamper-detection
> switches are not that secure as well.
Agreed; which is why I specifically said that it'll make the attack
more difficult but not impossible.
As with pretty much anything else security-related, it's really only a
matter of how much money and effort the attacker is willing to throw
at the problem, and how much money and effort the defender is willing
to throw at the problem of discouraging the attacker.
But the simple fact is that inside a VM, the defender is _always_
going to be at a serious disadvantage against an attacker who has
access to the hypervisor (whether legitimately or not). That's just a
consequence of how the technology works.
--
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de
prev parent reply other threads:[~2021-10-17 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <uM6-PtHBQkbrEyvAQeucVxnm9WiQA5NZVwPYOWjDhauBu6LELGKBNgkDMaJL18hVDEVimjXygTsCclr8MJsTTlJ5pungtSGkIAYXBPi6xg4=@protonmail.ch>
2021-10-14 19:56 ` [dm-crypt] Re: reg: Question on LUKS device's content exposure Michael Kjörling
2021-10-16 20:15 ` Arno Wagner
2021-10-17 10:20 ` Michael Kjörling [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=cde99332-54c8-4341-92f0-02ab5d7b19da@localhost \
--to=michael@kjorling.se \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).