public inbox for cryptsetup@lists.linux.dev
 help / color / mirror / Atom feed
From: Arno Wagner <wagner@arnowagner.info>
To: cryptsetup@lists.linux.dev
Subject: Re: Question about FAQ 5.21: "Why is there no "Nuke-Option"?"
Date: Fri, 7 Nov 2025 20:36:54 +0100	[thread overview]
Message-ID: <aQ5KVmEbO7SHp3Z0@tansi.org> (raw)
In-Reply-To: <ycc43yz54ybgnal5t3rcment6vjvanalx2g2z6rly4wxxpietn@nn222ctnfqaz>

On Thu, Nov 06, 2025 at 15:38:06 CET, techmetx11 wrote:
> After seeing GrapheneOS's implementation of the same design idea, I feel
> like this idea wasn't given much thought in the FAQ.
 
You feel incorrectly. This has been extensively discussed. 
 
> This paragraph ignores the fact that the TPMs that come with computers
> have improved on-par to the standard of HSMs, and are now integrated
> straight in the CPU in most cases, rather than being a seperate chip or
> card that can be simply bus-probed or manipulated physically.

They really have not. Not even remotely. 
 
> > Still, if you have a good use-case (i.e.  non-abstract real-world
> > situation) where a Nuke-Option would actually be beneficial, please let
> > me know.
> 
> Imagine if you were being tortured by people to unlock a hard drive that
> you didn't want them to see the contents of, and so you give them the
> password to hopefully make it so that it wipes the TPM/HSM/etc. of the
> computer and destroy any chance of unlocking the contents, thus making
> their job futile and saving information from ending up on your
> adversaries' hands (even if it meant it cost you your life)

This senario has been discussed here many times. It is not a 
valid reason to have a nuke option. Also note the cryptsetup
has no TPM integration as part of the project.  

Regards,
Arno Wagner

-- 
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

      parent reply	other threads:[~2025-11-07 19:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06 14:38 Question about FAQ 5.21: "Why is there no "Nuke-Option"?" techmetx11
     [not found] ` <aQzAAvW7wmbFoOrv@xed.ch>
2025-11-06 15:46   ` techmetx11
     [not found]     ` <DD9C9341-D528-4BE1-80D9-444F95185D49@va1der.ca>
2025-11-06 17:11       ` techmetx11
2025-11-06 22:46     ` Kurt Fitzner
2025-11-07  9:37 ` Milan Broz
2025-11-07 19:36 ` 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=aQ5KVmEbO7SHp3Z0@tansi.org \
    --to=wagner@arnowagner.info \
    --cc=arno@wagner.name \
    --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