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

How To: Config ShredOS to boot and automatically invoke clean command #279

Open
dgdomtar opened this issue Aug 28, 2024 · 3 comments
Open

Comments

@dgdomtar
Copy link

We are decomming devices to be given to a non profit. All we need to do essentially is run the Diskpart clean command to wipe the drives.

Can ShredOS be setup to automatically do this once it's booted via USB? IE no interaction?

@PartialVolume
Copy link
Owner

Yes, you can create a auto nuke device by editing the grub.cfg files and adding nwipe_options=" --autonuke". See https://github.com/PartialVolume/shredos.x86_64?tab=readme-ov-file#how-to-change-the-default-nwipe-options-so-the-change-persists-between-reboots

However, it obviously won't be using DiskPart which is Windows. I couldn't figure out what sort of wipe DiskPart clean is doing. Traditional block writing or ATA secure erase? Any Windows users know?

@gorbiWTF
Copy link

https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/clean

On master boot record (MBR) disks, only the MBR partitioning information and hidden sector information is overwritten.

On GUID Partition Table (gpt) disks, the gpt partitioning information, including the Protective MBR, is overwritten. There is no hidden sector information.

A for effort, I guess...

@PartialVolume
Copy link
Owner

https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/clean

On master boot record (MBR) disks, only the MBR partitioning information and hidden sector information is overwritten.
On GUID Partition Table (gpt) disks, the gpt partitioning information, including the Protective MBR, is overwritten. There is no hidden sector information.

A for effort, I guess...

I guess the clean command is not really for forensic destruction of data. Seems like the bare minimum it can get away with. With a few forensic recovery tools a lot of the data could be recovered quite easily. It does make you wonder how many unsuspecting people use clean thinking they deleted their data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants