Ticket #226 (new enhancement)

Opened 5 years ago

Last modified 5 years ago

Progressive corrupting of files as a wipe method

Reported by: pollution Owned by:
Priority: trivial Milestone: Eraser 6.1/6.2
Component: Core Version:
Keywords: Cc:
Processor Architecture: Blocked By: #279
Blocking: Operating System:

Description

This is an idea intended for mainly huge huge files which you would want to make harder (but not impossible) to restore any meaningful data pieces from it.

Normal wipes start at the beginning of the file and write to the end of it.

My method would write at random locations of the file slowly replacing all of its content the further Eraser runs the task. Letting this method run to the end would have the same end result as a normal wipe.

This method is supposed to be an enhancement on the "first and last 16KB" wipe.

Blocking

IdSummaryMilestone
#226Progressive corrupting of files as a wipe methodEraser 6.1/6.2

Blocked by

IdSummaryMilestone
#226Progressive corrupting of files as a wipe methodEraser 6.1/6.2
#279Implement Custom Erasure TypesEraser 6.1/6.2
#276Implement Eraser Registrar InterfaceEraser 6.1/6.2

Change History

comment:1 Changed 5 years ago by Joel

  • Blocked By 279 added
Note: See TracTickets for help on using tickets.