Ticket #226 (new enhancement)
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
| Id | Summary | Milestone |
|---|---|---|
| #226 | └ Progressive corrupting of files as a wipe method | Eraser 6.1/6.2 |
Blocked by
| Id | Summary | Milestone |
|---|---|---|
| #226 | └ Progressive corrupting of files as a wipe method | Eraser 6.1/6.2 |
| #279 | └ Implement Custom Erasure Types | Eraser 6.1/6.2 |
| #276 | └ Implement Eraser Registrar Interface | Eraser 6.1/6.2 |
Note: See
TracTickets for help on using
tickets.
