Eraser 6-rc2 released!

Published on December 13, 2008, by in Announcements.

Eraser 6 Release Candidate 2 is released, bringing with it about a dozen fixes (a few of them major!)

The list of changes:

RevisionDescriptionAuthor
672Authenticode certificate validation
The Authenticode certificate should be checked alone and not traced to the root certificate to allow for revocation
Joel
677-736Implemented an Explorer context menu
Shell integration allows for the queuing of tasks in the Eraser Task List.
Kaz/Joel
737-741
743-757
759-764
767-773
Implemented remote task creation
Other Eraser instances can now communicate with the main instance, giving more tasks to complete so that tasks can be controlled from one interface
Kaz/Joel
766Eraser now starts up together with the system.
This allows tasks to be marked Run on Restart
Joel
777Slightly better error loggingJoel
781Single-instance Eraser
Further work to allow a single instance of Eraser. This brings with it a few Vista UAC changes as well
Joel
792Bootstrapper progress bar
The bootstrapper progress bar usually remained at zero
Joel
793Create standard Windows Shortcuts for Eraser so Run as Administrator can be accessed.Joel
795-802Implemented NTFS MFT record erasure
The old code erroneously erased resident MFT records without erasing old entries.
Joel
806Erase all files in folder to ignore inaccessible files
The old code would completely stumble when a file or folder was inaccessible. The behaviour now is to just ignore the file/folder
Joel
807Allow cancellation of cluster tip erasuresJoel/Kaz
809Unused space erasures now include erasing the cluster tips of files outside the working directory of Eraser if the drive Eraser was on was being erased.Joel
811Time estimates are now based on a 15-second averageJoel

Of course, some of the old features missing still have not been implemented in rc2 are:

  • Erasures of Encrypted/Compressed/Sparse NTFS files (unlikely to be implemented, low-level undocumented APIs required)
  • FAT32 FAT erasures (unlikely to be implemented, low-level APIs required)

The main reason both are not done is because the method employed in v5 to erase such files will not work on Vista (even with UAC disabled). Until a solution to erase these on Vista (with/without UAC on) surfaces these will not be implemented (for safety reasons: we don’t want to corrupt drives.)

I’m certain the rc-1 beta testers were generally happy with it (thank you for helping, all 2393 of you!) and I wish all rc-2 testers the same! If you currently hold onto rc-1, the above list should give you even more reason to upgrade (it’s free and painless, anyway.)

Disclaimer: The security of the erasures has not been verified by internal or external entities. The code is still of beta quality and may not remove all traces of files with the confidence of Version 5. If you have security concerns, do use Version 5 while the security aspects of Version 6 are ironed out. It is however noteworthy that v6 uses only documented APIs for erasure and therefore the risk of corrupting your drives is lower than Version 5.

If you have read the disclaimer, follow the instructions about installing betas then Download it now.