Hi PrepHole. I come with thoughts of frying electronics and throwing access to your beloved HDD/SDD into the ether.
I'm about to embark on a DIY project for destroying keys to my hard disk in a very physical way.
The requirements:
1. Must be using a trusted platform module to encrypt your disk(s).
2. No recovery after trigger
3. Optionally remove encryption headers from hard drives.
My idea is this:
1. Use a boost converter wired to the trusted platform module and store a lethal charge to the TPM module in its capacitor.
2. Remote or local trigger.
3. Destroy LUKS, or other encrypted headers on trigger. (effectively removing the ability to unlock via password)
4. Zap TPM module and let out the magic smoke in the event headers can be restored from another breach to take care of key recovery.
or instead of having that autism just shred the hard drive after wiping it with software that just writes the drive over and over with garbage until nothing is there.
I'm trying to counter more severe theoretical autism.
if [ "$EUID" -ne 0 ]; then
echo "Please run as root" && exit 1
fi
if [ $# -eq 0 ]; then
echo "USAGE: randomize-disk.sh /dev/sdX" && exit 1
fi
if [[ $1 == /dev/* ]] && [[ -e $1 ]]; then
DISK="$(echo $1 | awk -F'/' '{print $3}')"
echo "Starting wipe for $1..."
else
echo "ERROR: Device must exist and start with /dev/*" && exit 1
fi
DISK_SIZE=$(</proc/partitions awk '$4=="'"$DISK"'" {print sprintf("%.0f",$3*1024)}')
for i in {1..7}; do
openssl enc -aes-256-ctr -pbkdf2 -nosalt
-pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)"
done
There have been papers of people reconstructing data from near dust. This is a take no prisoners situation. Physical destruction beyond electricity is not a possibility in this scenario.
nobody gives a shit enough about you to warrant this
Can one not destroy electronics for the fun of destroying electronics? Fricking christ, anon. I worked in security.
>fun
autism is not for fun
>There have been papers of people reconstructing data from near dust
Throw it into a bucket of gas and light it. Why would you come looking for the nerd's solution?
Because when the feds come knocking having some hard drives melting in a trash can in the fireplace might get them motivated into jamming a warrant up your ass. OP is trying to crowdsource a ‘pedos delight’ end run around file security.
Because dead man's switches and destruction are more fun.
Trying to crowd-source anything off this website is futile. I wrote a kernel module and hacked together a circuit. Hardly an end run around file security but I find increased security hilarious to be grouped with the p-word (who are generally just dumb and opting for steganography over real security).
I am not the first to dream this up, I just want a smaller and more affordable solution to a 1U rackspace full of thermite and a need for gas extraction.
>There have been papers
>near dust
[citation needed]
you made a claim... support it.
drilling holes in the disk is more than enough
go be a cyber terrorist somewhere else.
this.
heating the medium to over 500 degrees will remove permanently all magnetic data.
>There have been papers of people reconstructing data from near dust.
absolute bullshit
shred the thing and throw it in acid nobody is recovering shit then
disintegrate it with electrolysis
Just drill a hole in it you fricking nerd
>requirements
These are not requirements. These are an expression of your approach.
Requirements describe an existing state, an end state, and a limitations on the process by which to love from the former to the latter.
State: Working TPM and encrypted volumes.
End state: Destroyed TPM module via trigger of boost converter, LUKS headers removed, failure to boot.
Limitations: No physical damage beyond what can be provided from current, destruction of both header and keys in the event of a partial prior clone or found backup.
The kernel module is already written for triggering and removing LUKS headers. Going to a hackerspace tomorrow to throw together the hardware and find a place for it to sip power in an old laptop.
I can't even be moved to verbally smack you upside the head for being such a fricking useless, uncomprehending shit.
Do whatever you want. Don't come here looking for approval.
Get off Discord and do something with your life, anon. ffs
Get your head out of your ass and realize: you're not as smart as you think you are, your craving attention and approval is indicative of narcissistic personality disorder, and no one cares about you.
Child.
Have you heard of the Dunning-Kruger effect, anon? I don't think I'm smart. Sorry for DIYing in a DIY board, you insecure homosexual. I'm shouting into an anonymous void... what kind of projection mindfrick turns that into a narcissistic attention craving?
IIRC there's a standing bounty for a method of disk destruction that fits in a standard server HDD slot, and stands up to forensic recovery efforts. Heard about it at defcon several years ago.
I mention this mostly because I don't think you're going to figure it out, but if you do you might as well make some beer money.
what about thermite?
This is exactly where this comes from. Deviant and Zoz did the 1U above and below. Then that one dude tried to do it "better" and was arrested for his basement/kid dying. This is a less volatile, bits left standing but not accessible.
This is PrepHole anon. Frick your citation. TLAs collect/exploit physically damaged drives for recovery. This is what happens in Iraq. If they are not completely shredded/burned they are instructed to send them back. Been told the same from DoD contractors I've worked with
?t=296
HDDs are notoriously unreactive. Frick your acid anon.
>If they are not completely shredded/burned
Far cry from dust moron.
Easy. Oxy/Mapp torch applied to the hard drive with a cutting flame.
I see what you're going for, and the only solution I can think of is to apply as much current to the drive as possible on command, like a bank of capacitors on a switch or something
I'm not really sure of any home computer system that has the capability to do rapid damage to a hard drive without serious modification or a completely separate device
leave your drives out in the open and buy a hammer from the hardware store.
don't make it more complicated than it needs to be, recovering data from dust sounds like FUD.