Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cryptsetup Nuke Keys Patch #921

Open
marmarek opened this issue Mar 8, 2015 · 5 comments
Open

Cryptsetup Nuke Keys Patch #921

marmarek opened this issue Mar 8, 2015 · 5 comments
Labels
C: other cryptography This issue pertains to cryptography. help wanted This issue will probably not get done in a timely fashion without help from community contributors. P: major Priority: major. Between "default" and "critical" in severity. security This issue pertains to the security of Qubes OS.

Comments

@marmarek
Copy link
Member

marmarek commented Mar 8, 2015

Reported by anonymous on 9 Nov 2014 21:03 UTC
Feature Request: Cryptsetup Nuke Keys Patch

Upstream Provider: Kali Linux

Kali Linux webpage: kali.org

Nuke Keys Git Repo: https://github.com/offensive-security/cryptsetup-nuke-keys

Arch Linux AUR package: https://aur.archlinux.org/packages/cryptsetup-nuke-keys/

Where: dom0

Purpose: Allows user to erase keyslots using an alternate "nuke" password.
Easier than other erasure methods.
Does not require input of decryption password.
Resistant to user error via overwriting non-keyslot data using alternate erasure methods.

How: User chooses a 'nuke' passphrase.
Upon using nuke passphrase, all keyslots are wiped, rendering drive unusable.
Keyslots can be restored later using keyslot backups.

Note: May require modification from original files to work.

Migrated-From: https://wiki.qubes-os.org/ticket/921

@marmarek marmarek added enhancement C: other P: major Priority: major. Between "default" and "critical" in severity. labels Mar 8, 2015
@marmarek
Copy link
Member Author

marmarek commented Mar 8, 2015

Modified by marmarek on 11 Nov 2014 02:44 UTC

@marmarek marmarek added this to the Release 3 milestone Mar 8, 2015
@marmarek
Copy link
Member Author

marmarek commented Mar 8, 2015

Comment by John on 2 Dec 2014 05:53 UTC
The pros and cons are described in section 5.21 of the official FAQ of the cryptsetup project:

https://github.com/mbroz/cryptsetup/blob/master/FAQ

In short: it fails to increase security to any significant degree.

@marmarek marmarek modified the milestones: Release 3.1, Release 3.0 May 23, 2015
@marmarek marmarek modified the milestones: Far in the future, Release 3.1 Oct 3, 2015
@andrewdavidwong andrewdavidwong added the help wanted This issue will probably not get done in a timely fashion without help from community contributors. label Jun 12, 2016
@andrewdavidwong
Copy link
Member

andrewdavidwong commented Jun 30, 2016

Recent discussion about the usefulness of this feature:
https://groups.google.com/d/topic/qubes-users/1Qu0v2b7-bg/discussion

@andrewdavidwong
Copy link
Member

Older thread on the same topic:
https://groups.google.com/d/msg/qubes-users/tKOVanAupFE/jkOYaN44zksJ

@andrewdavidwong andrewdavidwong removed this from the Release TBD milestone Aug 13, 2023
@DemiMarie
Copy link

To be effective, this needs to either:

  1. Store the key in (and only in) a TPM that supports secure erase.
  2. Use the disk secure erase functionality.

Otherwise it must be assemed that the key can be recovered (at significant expense) by someone with specialized tools and prolonged physical access.

@andrewdavidwong andrewdavidwong added cryptography This issue pertains to cryptography. security This issue pertains to the security of Qubes OS. labels Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: other cryptography This issue pertains to cryptography. help wanted This issue will probably not get done in a timely fashion without help from community contributors. P: major Priority: major. Between "default" and "critical" in severity. security This issue pertains to the security of Qubes OS.
Projects
None yet
Development

No branches or pull requests

3 participants