Emergency Data & Login Nuke Tool (Bugfish-Nuke)
from Bugfish@lemmy.bugfish.eu to privacy@lemmy.ml on 14 May 00:53
https://lemmy.bugfish.eu/post/153

Hello there!

just updated a previous mentioned tool which has been in discussion here and wanted to share updates on the software status.

The software is in my opinion finished for now and tutorial videos are available, do not hesitate to ask for features if anything is missing.

Github URL: https://github.com/bugfishtm/bugfish-nuke
Documentation: https://bugfishtm.github.io/bugfish-nuke/

Features

Security Notes

Have a great one
Bugfish

#privacy

threaded - newest

DirigibleProtein@aussie.zone on 14 May 02:40 next collapse

Just encrypt the entire disk. In an emergency, turn the power off.

Bugfish@lemmy.bugfish.eu on 14 May 03:25 next collapse

Yes this would be more secure and recommended

Nicro@discuss.tchncs.de on 14 May 08:51 collapse

And have a script to secure erase the key material. Much faster and will prevent forced/coerced unlocks.

Bugfish@lemmy.bugfish.eu on 14 May 18:09 collapse

This will be added as a functionality in the next release, thanks for the hint.

cy_narrator@discuss.tchncs.de on 14 May 15:46 next collapse

Have you considered if secure deletion will work as expected when using SSDs or SD Card? I heard the only way to actually delete something is to fill it with gibbirish and format it

Bugfish@lemmy.bugfish.eu on 14 May 18:05 collapse

Really good point. Data Deletion on SSDs and NVMEs are handled differently. (I dont really know about SD Cards but it may be similar)

NVMA/SSD Data Deletion follows 3 Steps

  • You delete / overwritte a file (overwrite does not really mean the old content is lost on the ssd, it may be in the NAND storage)
  • The TRIM Features starts periodically and markes the data / content you deleted as erased (this functionality can be triggered by software, i will implement this trigger)
  • The problem is the last step, Garbage Collection: This will erase the data finally, and then the probability is REALLY low someone will restore it. Before garbage collection is complete, there are ways to restore with advanced techniques or help of the manufacturer.

So best is to activate the TRIM Feature when Its implemented on the next update, but this feature will also be auto-executed by the windows system. - Best is to wait hours (its hard to know when garbage collection is finished) after the trim feature has been enabled to be sure garbage collection has deleted the content/files.

But for security measures it still can help to delete the data, even if the garbage collection is not finished. The risk for recover depends than on how many resources the opponent is ready to acquire to get to that data. It will make the recover process difficult without special forensics software etc.

Best and most secure way is to encrypt your data at all so none one can access even if they have the files.

Blemgo@lemmy.world on 14 May 21:47 collapse

Is there a benefit from this over the inbuilt Secure Erase functionality in most SSDs/NVMEs? To my knowledge, it instantly dumps the current from all cells, emptying the data on it.

Furthermore, another issue with SSDs/NVMEs is that it automatically excludes bad blocks, meaning that classic read/write operations can’t even reach those blocks anyways. Theoretically that feature could also be used against you to preserve the data on the disk by marking all blocks as bad, rendering them as inaccessible by the file system.

Of course there’s also the issue of Secure Erase not being implemented properly in some drives, leading to the bad blocks not being touched by the hardware chip during that procedure.

Bugfish@lemmy.bugfish.eu on 15 May 00:52 collapse

The benefit is to delete data and execute operations (as deleting logins) in emergency situations when time is a factor. The manufactures inbuilt secure erase function is definitely the better way to make your data unrecoverable, but can take more time and may not be suitable in emergency situations.

Its not planed to add something against bad block data in bugfish-nuke, my recommendation to be safe in that matter:

  • Use the manufactures secure delete software (maybe it will detect and delete the bad blocks, no guarantees)
  • Encrypt the whole SSD, so bad blocks wont be a problem because they contain encrypted snippets.
  • If you want to get rid of the ssd drive anyway, screw it open, remove the NAND chips, smash them with a hammer in little pieces and flush it down the toilette, no one will ever recover that :)
Blemgo@lemmy.world on 14 May 21:52 collapse

Quick question about the overwrite passes: is it overwritten with random numbers or is there a sequence of passes?

Bugfish@lemmy.bugfish.eu on 15 May 00:42 collapse

Greetings

The files are overwritten with random numbers (random bytes) for each pass. Specifically, for each overwrite pass, the method fills the file with cryptographically secure random data generated by RandomNumberGenerator.Create(). There is no sequence of different patterns (such as 0xFF, 0x00, then random) in my implementation-each pass is random data only.

If you are interested in different overwrite patterns let me know, then i may will implement a solution to choose methods. Overwrite passes count can be set inside the software after hitting the launch button in the confirmation process.