Ticket #141 (closed enhancement: fixed)

Opened 6 years ago

Last modified 5 years ago

Better method description.

Reported by: Overwriter Owned by: Joel
Priority: minor Milestone: Eraser 6.0
Component: Documentation Version: 6.0.3.847
Keywords: Cc:
Processor Architecture: Blocked By:
Blocking: Operating System:

Description

Eraser V6 Beta 3

When a user drops down the erase methods it would be nice if when the user hovered over a particular method that an information box would appear describing the method in more detail.

Blocking

IdSummaryMilestone
#141Better method description.Eraser 6.0

Blocked by

IdSummaryMilestone
#141Better method description.Eraser 6.0

Change History

comment:1 Changed 6 years ago by Joel

  • Status changed from new to assigned
  • Owner set to Overwriter
  • Version set to 6.0.3.847
  • Component changed from Core to Documentation
  • Milestone set to Eraser 6.0

Hmm, what sort of detail will be good?

comment:2 Changed 6 years ago by Overwriter

Example.

British HMG IS5 (Enhanced) (3 passes)

British HMG IS5 (Enhanced) is a three pass overwriting algorithm. The first pass is with zero’s, second pass with ones and the last pass with random bytes. The last pass is verified.

comment:3 Changed 6 years ago by Overwriter

I just found this list that might be helpful, I think someone posted this for me on a different forum. I really must keep a record of whats going on !! :o)

Fast (1 pass)
The fastest wiping scheme. Your data is overwritten with zeroes.

  • British HMG IS5 (Baseline) (1 pass)

Your data is overwritten with zeroes with verification.

  • Russian GOST P50739-95 (2 passes)

GOST P50739-95 wiping scheme calls for a single pass of zeroes followed by a single pass of random byte.

  • British HMG IS5 (Enhanced) (3 passes)

British HMG IS5 (Enhanced) is a three pass overwriting algorithm: first pass - with zeroes, second pass - with ones and the last pass with random bytes (last pass is verified).

  • US Army AR380-19 (3 passes)

AR380-19 is data wiping scheme specified and published by the U.S. Army. AR380-19 is three pass overwriting algorithm: first pass - with random bytes, second and third passes with certain bytes and with its compliment (with last pass verification) .

  • US Department of Defense DoD 5220.22-M (3 passes)

DoD 5220.22-M is three pass overwriting algorithm: first pass - with zeroes, second pass - with ones and the last pass with random bytes. With all passes verification.

  • the US Department of Defense DoD 5220.22-M (E) (3 passes)

DoD 5220.22-M (E) is three pass overwriting algorithm: first pass - with certain bytes, second pass - with its complement and the last pass - with random bytes.

  • NAVSO P-5239-26 (RLL)

NAVSO P-5239-26 (RLL) is three pass overwriting algorithm with last pass verification.

  • NAVSO P-5239-26 (MFM)

NAVSO P-5239-26 (MFM) is three pass overwriting algorithm with last pass verification.

  • the US Department of Defense DoD 5220.22-M(ECE) (7 passes)

DoD 5220.22-M(ECE) is seven pass overwriting algorithm: first and second passes - with certain bytes and with its compliment, then two passes with random character, then two passes with character and its complement and the last pass - with random character.

  • Canadian RCMP TSSIT OPS-II (7 passes)

RCMP TSSIT OPS-II is seven pass overwriting algorithm with three alternating patterns of zeroes and ones and the last pass - with random character (with last pass verification).

  • German VSITR (7 passes)

The German standard calls for each sector to be overwritten with three alternating patterns of zeroes and ones and in the last pass with character.

  • Bruce Schneier (7 passes)

The Bruce Schneier wiping algorithm has seven passes: first pass - with ones, the second pass - with zeroes and then five times with random characters.

comment:4 Changed 6 years ago by Joel

Actually verification isn't performed. We only implement the wiping procedure.

comment:5 Changed 6 years ago by Overwriter

“Actually verification isn't performed. We only implement the wiping procedure.”

Oops, then can we claim to be performing to these standards then if we, err, aren’t doing them ?

How can I write about this if I don’t know what Eraser is doing ?

I wish I hadn’t been volunteered for the documentation job ! Volunteering should be voluntary, surely by definition ! I was happy beta testing, moderating and answering questions on the forum, deleting spammers, trying to drum up some support, making feature requests, posting on other forums about Eraser and organising the forensic team. All while holding down a full time job !

But oh no, that wasn’t enough was it……oh no probably just me being lazy, I think I should stick a brush up my a#se and sweep the floor while I am running around like an idiot !!

Ha ha !

I’ll try to sort this, but I could do with your help Joel, you know better than me what Eraser is doing. Do I assume it is doing everything else just not the verification pass ?

Thanks. :o)

comment:6 Changed 5 years ago by Joel

The verification can't be performed. If a pass is to write random data, how will Eraser know that data is indeed random and not an error in the information?

comment:7 Changed 5 years ago by Joel

  • Owner changed from Overwriter to Joel
  • Status changed from assigned to accepted

I've included this into the draft documentation for Eraser 6.

comment:8 Changed 5 years ago by Joel

There are factual inaccuracies in the passes, apparently.

comment:9 Changed 5 years ago by Joel

  • Status changed from accepted to closed
  • Resolution set to fixed

Factchecked and accepted.

Note: See TracTickets for help on using tickets.