Skip to content
This repository has been archived by the owner on Dec 8, 2022. It is now read-only.

Nuking cryptsetup keyslots #32

Open
1989gironimo opened this issue Jan 9, 2019 · 3 comments
Open

Nuking cryptsetup keyslots #32

1989gironimo opened this issue Jan 9, 2019 · 3 comments
Labels
Custom Command Not officially supported

Comments

@1989gironimo
Copy link

Shamelessly stolen from @HulaHoopWhonix via github/usbkill:
I don't know if custom commands are supported but nuking cryptsetup keyslots would be a good option.

@Lvl4Sword
Copy link
Owner

I like this idea and will add it to my todo list.

@Lvl4Sword Lvl4Sword added Linux This issue targets Linux Future Something that is planned for a future release labels Jan 9, 2019
@Lvl4Sword
Copy link
Owner

Lvl4Sword commented Mar 16, 2019

According to https://wiki.archlinux.org/index.php/Dm-crypt/Device_Encryption :
luksErase is used to quickly remove all active keys.
So, that would probably be a good idea to use.
Though, testing this will require a VM as to ensure I don't nuke any system I'm testing on.

Looking at https://superuser.com/a/1168933 , there will be a prompt that requires a YES input.
echo -n "YES" | cryptsetup luksErase /dev/sdaX - should work for this, but I'll have to test.

@Lvl4Sword Lvl4Sword added the Custom Command Not officially supported label Mar 16, 2019
@Lvl4Sword
Copy link
Owner

I labeled this "Custom Commands", as this'll be something that will be a lot easier to setup when custom commands are done.
Any custom commands won't be officially supported, so any issues with them won't be addressed.

@Lvl4Sword Lvl4Sword removed Future Something that is planned for a future release Linux This issue targets Linux labels Mar 16, 2019
@Lvl4Sword Lvl4Sword changed the title Custom Commands: Nuking cryptsetup keyslots Nuking cryptsetup keyslots Apr 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Custom Command Not officially supported
Projects
None yet
Development

No branches or pull requests

2 participants