this post was submitted on 30 Dec 2023
152 points (94.7% liked)

Asklemmy

43963 readers
1616 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy ๐Ÿ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 9 points 11 months ago* (last edited 11 months ago) (2 children)

I can't remember but having my hard drive encrypted, I believe there is a single file that messing with it would render the drive not decryptable.

[โ€“] [email protected] 1 points 11 months ago* (last edited 11 months ago)

Here is the command that will render a LUKS encrypted device un recoverable
From the documentation.

5.4 How do I securely erase a LUKS container?

For LUKS, if you are in a desperate hurry, overwrite the LUKS header and key-slot area. For LUKS1 and LUKS2, just be generous and overwrite the first 100MB. A single overwrite with zeros should be enough. If you anticipate being in a desperate hurry, prepare the command beforehand. Example with /dev/sde1 as the LUKS partition and default parameters:

head -c 100000000 /dev/zero > /dev/sde1; sync