Feature #7313

Set a non-arbitrarily chosen allowed value for memory erasure coverage

Added by anonym 2014-05-27 04:51:47 . Updated 2014-05-27 05:16:54 .

Status:
Confirmed
Priority:
Low
Assignee:
Category:
Test suite
Target version:
Start date:
2014-05-27
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

In the step “I find very few patterns in the guest’s memory” in memory_erasure.feature we set max_coverage = 0.0025, i.e. we allow less than 0.25% of memory to not be wiped. The efficiency of our memory erasure approach seem to differ depending on kernel version, architecture (64-bit vs 32-bit) and the phase of the moon, so we sometimes have to arbitrarily bump it as well.

We should come up with a sound value for max_coverage, preferably based on Hard Science™.

Subtasks

History

#1 Updated by intrigeri 2014-05-27 04:56:35

  • Subject changed from Set a non-arbitrary allowed maximum for to Set a non-arbitrary chosen allowed value for memory erasure coverage

#2 Updated by anonym 2014-05-27 05:16:54

  • Subject changed from Set a non-arbitrary chosen allowed value for memory erasure coverage to Set a non-arbitrarily chosen allowed value for memory erasure coverage
  • Priority changed from Normal to Low