GitHub - PartialVolume/shredos.x86_64: Shredos Disk Eraser 64 bit for all Intel 64 bit processors as well as processors from AMD and other vendors which make compatible 64 bit chips. ShredOS - Secure disk erasure/wipe
github.com
Shredos Disk Eraser 64 bit for all Intel 64 bit processors as well as processors from AMD and other vendors which make compatible 64 bit chips. ShredOS - Secure disk erasure/wipe - PartialVolume/sh...

ShredOS is a USB bootable (BIOS or UEFI) small linux distribution with the sole purpose of securely erasing the entire contents of your disks using the program nwipe.

  • Deckweiss@lemmy.world
    2·
    3 days ago

    I don’t think we are arguing about the same scenario at all.

    Here is an example of what I have in mind:

    1. I work as a freelancer on a customers project.
    2. In my computer I have an 128G NVME (15$) which is seperate from my OS where I put the data the customer entrusted me with and the project files
    3. After the project, I take that NVME out, put it in a box on a shelf and buy a new one (15$) for the next project
    4. Some time after project completion, I can either trash the drives or send them in bulk to some data erasure service, or leave them on my shelf for ever.

    As opposed to

    1. After the project, I take that NVME-1 out, put it in a box on a shelf and buy a new one for the next project (NVME-2)
    2. for the project after that, I again take out NVME-2 and put it on a sheld, I get NVME-1 from my shelf, put it in, run secure erase for multiple hours before I can start working on the next project.

    My argument is, that the cost of the first process is negligible compared to the effort and hassle of the second process, for a freelancer that earns over 6x the cost of such drive per hour.

    • x00z@lemmy.worldEnglish
      3·
      2 days ago

      My scenario was indeed handling the drives of customers themselves.

      For your scenario I would just use some encrypted filesystem.