Ticket #208 (closed enhancement)
Slow free space wipe
| Reported by: | Posts | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | Eraser 6.1/6.2 |
| Component: | Core | Version: | |
| Keywords: | Cc: | ||
| Processor Architecture: | Blocked By: | ||
| Blocking: | Operating System: |
Description
Current full usage renders the computer useless, and requires the computer to be active when not being used.
I suggest a gradual write X-MB every Y-Seconds.
And only write when there has been user activity(mouse/keyboard) within Z-minutes. Yes, this is the opposite of what you usually see, I want the computer to sleep while the user is not using it.
Erase method: append to file(single pass), until 5-GB of free space is left, delete the big file and start over. (better than nothing, and it makes me feel safer than having some low level method mucking around) yes, an infinite loop option, and restarting will pickup where it left off.
Blocking
| Id | Summary | Milestone |
|---|---|---|
| #208 | └ Slow free space wipe | Eraser 6.1/6.2 |
Blocked by
| Id | Summary | Milestone |
|---|---|---|
| #208 | └ Slow free space wipe | Eraser 6.1/6.2 |
Change History
Note: See
TracTickets for help on using
tickets.
I don't think this will be of any use - the OS is sticky. After a file has been deleted it may end up using the same space the old file used to sit on and there will be areas which don't get erased. Is this okay for your threat model?