maltob / diskslaw Goto Github PK

Describe the bug
On test laptop using enhanced security erase did not wipe drive

To Reproduce

1. Boot laptop with mechanical drive that supports security erase
2. Wait for security erase/wipe to finish
3. Validation will fail

Expected behavior
Enhanced security erase if failed should fall back to security erase, then shred.

Additional context
For v0.3 defaulted to using shred on rotational disks.
Further testing will be needed to see if this drive doesn't support it or if the program is incorrect.
Drive log does show SG_IO Bad Sense Data error, perhaps we should check for that and fall back to shred on rotational.

Is your feature request related to a problem? Please describe.
If you gracefully shutdown the machine in the middle of security erase the disk security password will remain set, this will prevent disk access until it is removed as the password is null byte padded inhibiting the ability for a user to enter the password on startup.

Describe the solution you'd like
Have removal of the password at shutdown if it is on a drive.

Describe alternatives you've considered
Only selecting a 32 byte long password will allow entering the password at startup, but would cause additional headache if needed in bulk.
Changing to a 32 byte password should still be considered as well with the above shutdown solution so it can be entered on bootup if needed.

Testing of additional models of hardware would be useful
Model Support page on Wiki

Tablets

• Limited RAM
• Limited input methods
• UEFI only

Desktops

• Mechanical drives that support secure erase

Laptops

• NVMe drives
• SSD drives
• USB C/Thunderbolt
• UEFI only

USB Hubs

• Flash drive + keyboard
• USB C, Thunderbolt, different chipsets

Describe the bug
Closing the lid on the laptop causes the screen to go blank and not display progress bar

To Reproduce
Steps to reproduce the behavior:

1. Start laptop wipe
2. Suspend and resume
3. While wiping close the lid
4. Open the lid, the power button will show green but the screen stays blank.

Expected behavior
Screen would either stay on or return to operation when lid is opened

Device:

• Manufacturer: Dell
• Type : Laptop
• Video Card : Intel HD Series + NVidia GTX 10X0

Additional Information
Did not await to see if the screen would return after wiping finished.
This is after coming out of suspend

Describe the bug
Security Erase status text causes the dialog to be shifted

To Reproduce
Steps to reproduce the behavior:

1. Boot v0.2 on a machine with a Security Erase capable drive
2. Enter suspend and exit suspend
3. The output of the command will appear on the screen and the dialog will be incorrectly formatted

Expected behavior
No text should appear on the screen
The dialog should look as expected

Device

• Mechanical Drive supporting secure erase

Is your feature request related to a problem? Please describe.
@humm3r1 is testing automatic wake up to their fork.
Currently you need to power back on the machine, rtcwake can wake up machines after a certain period of time.

Describe the solution you'd like
Ask the machine to suspend to memory and power itself on using rtc, which @humm3r1 has tried in their fork with suspend to disk.

Describe alternatives you've considered
WOL proxy would require another machine for the wakeup

Additional context
humm3r1@8a91036

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

It would be nice to save the wipe data / reports to a server. This way I can validate and prove a device was wiped and have a record of it.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Perhaps a POST command over HTTPS or a similar way of appending a line to the bottom of a csv or log file.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

I haven’t tried to implement myself just yet but will try and contribute this as a feature to the project. Should be easy enough to do.

Loaded to UISB drive, the formatting did not show any advancement after 1 hours. I exited and rebooted.

The HDD is now locked with a password, of courfse I have no idea what that password would be!

Not that it matters for this machine but I wish to set up a friend in business to wipe their own drives, this could be a problem. If I knew the password it would help to work through the jobs.

Is your feature request related to a problem? Please describe.
UEFI is the future, we should ensure support for booting from UEFI over network and USB

Describe the solution you'd like
To be able to wipe from either network or USB drive using UEFI only

Describe alternatives you've considered
Legacy boot, this is expected to go away and several devices are already UEFI only.

Additional context
https://www.zdnet.com/article/intel-were-ending-all-legacy-bios-support-by-2020/

Is your feature request related to a problem? Please describe.
Having automatic copying of the results to a USB drive or other media would allow easier record keeping of drives/PC's that have been erased

Describe the solution you'd like
When DiskSlaw completes, copy it's CSV over to a USB drive with a name like:
DiskSlaw-{SERIAL}-{TIME}.csv

Describe alternatives you've considered
Custom scripts can currently be utilized to provide this, but it would be more useful to provide this on the stock image.

Describe the bug
DiskSlaw is not wiping physical machines. Detects "Frozen SSD" even in machines with mechanical drives. It looks like it tries to wipe the drives, but goes to 100% almost instantly, and shows (F) on the status line indicating it failed.

To Reproduce
Steps to reproduce the behavior:

1. Boot DiskSlaw on a Dell machine (Latitude 5550/5450/5570, Precision 3510/3520) from USB.
2. When prompted (as it detects a frozen drive), let it sleep. Resume by pressing power button since keyboard wake does not work.
3. Watch the progress, and it will go to 100% (F) almost immediately.

Expected behavior
I expect it to begin wiping the drives with the erase commands, instead of instantly failing.

Additional context
I am more than happy to help work on this with you and test against my machines. My workplace is looking for a tool that can detect and wipe SSD's/HDD's properly (so that we only shred on mechanical drives and not overwrite the entire SSD and kill it). I took a quick peek and so far I am unsure why it is acting up. I will try against the same hardware with manual commands from your script to see what happens.

Is your feature request related to a problem? Please describe.
SDA/SDB doesn’t tell us what was wiped very well, we should pull UUID and model/name as well

Describe the solution you'd like
Columns added to CSV for name, model and uuid.

Is your feature request related to a problem? Please describe.
Many IT departments run Windows, we should ensure we can build the ISO under Windows Subsystem for Linux

Describe the solution you'd like
Support to run the build script from within the default Ubuntu based WSL and have it generate the ISO.
From here they can use RUFUS to create the disks easily.

Describe alternatives you've considered
A VM or another host requires maintaining two operating systems and wouldn't work as well on smaller or lower end devices like a Surface Pro 2.