Ticket #147 (accepted enhancement)

Opened 6 years ago

Last modified 4 years ago

Ballast File Creation.

Reported by: Overwriter Owned by: Joel
Priority: minor Milestone: Eraser 6.1/6.2
Component: Core Version: 6.0.3.847
Keywords: Cc:
Processor Architecture: Blocked By: #363
Blocking: Operating System:

Description

I think it would be a great feature for Eraser V6 to enable the user to make ballast files.

A ballast file is a file that is used by Eraser users to fill up free space on a very large hard drive so regular free space erasures can be performed in much quicker time as the ballast files reduce the free space on the disk.

This would also help Truecrypt users with plausible deniability (yes I am still banging on and on about that !).

How it would work.

A user would have say a 500GB disk. Say 50GB was used with OS and some storage. If this user wishes to wipe his free space he would have to wipe 450GB of free space and also presumably the cluster tips of the first 50GB.

This would obviously take a long time and it would add considerable wear to the drive. In order to help the user Eraser should have an option to create ballast files.

The user should be able to open Eraser, click the “Create Ballast File” button and be presented with a new window.

Within this new window there should be an option to choose how many ballast files to make, a drop down ballast file size KB,MB,GB, a naming prefix (which could be left blank in which case a random name will be created) and to which drive they are to be saved.

The ballast files should be created with Erasers CSPRNG pass as this will help the Truecrypt plausible deniability feature as a truly random output from Eraser should be no different to a Truecrypt volume.

So as for the example above the user would perhaps select the following settings.

10 x 40GB files. (This would take up the bulk of the free space, the 40GB chunks can be deleted when a lot of drive space needs releasing).

4 x 10GB files. (This will enable fine tuning when only a small amount of free space is required at a later date).

So the user has created 440GB of ballast files reducing the free space to erase to only 10GB plus cluster tips.

Truecrypt users can claim their Truecrypt volumes are actually Eraser ballast files so there is no volume.

Thoughts Joel ?

Blocking

IdSummaryMilestone
#147Ballast File Creation.Eraser 6.1/6.2

Blocked by

IdSummaryMilestone
#147Ballast File Creation.Eraser 6.1/6.2
#363Plugin Code ReviewEraser 6.1/6.2

Change History

comment:1 Changed 6 years ago by Joel

  • Milestone set to Eraser 6.0

comment:2 Changed 6 years ago by Joel

  • Status changed from new to accepted
  • Owner set to Joel
  • Milestone changed from Eraser 6.0 to Eraser 6.1/6.2

Sounds like an idea, but it'll have to wait, unfortunately.

Or users could just resize their partition.

comment:3 Changed 6 years ago by cjax

I think it would be a good idea.

Regarding the generation of the random output I am working on a concept that ensures the generated output is provably secure. These files could be initially very large and their size could be reduced if it is needed in multiples of cluster sizes (No need for multiple files).

The only thing though would be to lock the file system extent so the DefargAPI doesn't move these files around too much, or does that not matter?

comment:4 Changed 5 years ago by Joel

An implication of this ticket is that for Eraser 6.1 the plugin architecture must be extended such that developers can cause their tools to be discovered. Perhaps a "tools" menu beside the Settings toolbar item?

comment:5 Changed 4 years ago by Joel

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