Ticket #22 (new enhancement)

Opened 6 years ago

Last modified 5 years ago

MFT and Directory Entries erasure

Reported by: Overwriter Owned by:
Priority: critical Milestone: Eraser 6.1/6.2
Component: Core Version:
Keywords: Cc:
Processor Architecture: Blocked By: #23, #279
Blocking: Operating System:

Description

So a user can frequently just clean the MFT at will, not destroy it. Actually that would also be useful to be able to right click on other drives and clean their MFT’s, FAT’s and directory entries.

Related: If time was a factor, I wonder if it might be better to overwrite the MFT first then free-space and finally cluster tips ? The MFT shows a record of deleted file names and takes seconds to clean. If the MFT was wiped clean first surly this would offer more practical security much quicker in case of interruption ?

Blocking

IdSummaryMilestone
#22MFT and Directory Entries erasureEraser 6.1/6.2

Blocked by

IdSummaryMilestone
#22MFT and Directory Entries erasureEraser 6.1/6.2
#279Implement Custom Erasure TypesEraser 6.1/6.2
#276Implement Eraser Registrar InterfaceEraser 6.1/6.2
#23Make ghost MFT-records more emptyEraser 6.1/6.2

Change History

comment:1 Changed 6 years ago by Joel

  • Milestone set to Eraser 6.1/6.2

comment:2 Changed 5 years ago by Joel

  • Priority changed from major to critical
  • Component set to Core

comment:3 Changed 5 years ago by Joel

  • Blocked By 276 added

We need to be able to allow plugins to define new types of tasks before this can be implemented.

comment:4 Changed 5 years ago by Joel

  • Blocked By 279 added; 276 removed

comment:5 Changed 5 years ago by Joel

  • Blocked By 23, 203 added

comment:6 Changed 5 years ago by BloodySword

  • Blocked By 203 removed

(In #203) I think it is very unsecure to do so, what if eraser crashes while processing or the drive is attached via usb and the usb protocol begins to hang?

Note: See TracTickets for help on using tickets.