Ticket #208 (closed enhancement)

Opened 6 years ago

Last modified 6 years ago

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:


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.


#208Slow free space wipeEraser 6.1/6.2

Blocked by

#208Slow free space wipeEraser 6.1/6.2

Change History

comment:1 Changed 6 years ago by Joel

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?

comment:2 Changed 6 years ago by Joel

  • Status changed from new to pending

comment:3 Changed 6 years ago by Joel

  • Milestone set to Eraser 6.1/6.2

comment:4 Changed 6 years ago by trac-robot

  • Status changed from pending to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

Note: See TracTickets for help on using tickets.