Feature #7468

Replace our memory erasure implementation with the wiperam package

Added by intrigeri 2014-06-29 10:29:31 . Updated 2017-04-05 17:58:19 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2014-06-29
Due date:
% Done:

50%

Feature Branch:
feature/7468-wiperam-deb
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

That package will be shared with Freepto, and possibly Whonix, and ideally uploaded to Debian some day.


Subtasks


Related issues

Related to Tails - Bug #7183: Fix memory erasure when booted with systemd Resolved 2014-05-09 2015-06-01
Related to Tails - Feature #6006: More efficient memory wipe Rejected
Blocked by Tails - Feature #5472: Automatically test behavior on boot medium removal Resolved 2016-01-15

History

#1 Updated by intrigeri 2014-06-29 10:29:50

  • Tracker changed from Bug to Feature

#2 Updated by intrigeri 2014-06-29 10:31:52

  • related to Bug #7183: Fix memory erasure when booted with systemd added

#3 Updated by intrigeri 2014-06-29 10:32:56

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10
  • Starter changed from Yes to No

An initial implementation was pushed, and seems to work. Now have to have it go through our automated test suite.

Note that this package can’t be uploaded to Debian before it works with systemd too: see Bug #7183.

#4 Updated by emmapeel 2014-08-16 07:35:42

#5 Updated by intrigeri 2014-11-20 22:53:45

Next step: import into wiperam the partial rewriting to native systemd unit files, that was done in feature/jessie.

#6 Updated by intrigeri 2015-06-19 04:24:54

  • % Done changed from 10 to 20

intrigeri wrote:
> Next step: import into wiperam the partial rewriting to native systemd unit files, that was done in feature/jessie.

Done the initial porting work. Next step: test it in Tails/Jessie.

#7 Updated by intrigeri 2015-07-08 08:44:56

intrigeri wrote:
> Done the initial porting work. Next step: test it in Tails/Jessie.

Updated erase_memory.feature in feature/jessie, which should ease said testing.

#8 Updated by intrigeri 2015-07-08 10:04:37

  • Assignee changed from intrigeri to anonym
  • Target version set to Tails_2.0
  • % Done changed from 20 to 50
  • QA Check set to Ready for QA

Passes erase_memory.feature => please review and merged into feature/jessie :)

#9 Updated by intrigeri 2015-07-08 10:47:42

  • blocked by Feature #5472: Automatically test behavior on boot medium removal added

#10 Updated by intrigeri 2015-07-08 10:48:22

Note that I didn’t test emergency shutdown => marked as blocked by Feature #5472.

#11 Updated by intrigeri 2015-11-12 09:07:31

  • Assignee changed from anonym to intrigeri

intrigeri wrote:
> Note that I didn’t test emergency shutdown => marked as blocked by Feature #5472.

Merged current feature/jessie into the topic branch, will test emergency shutdown by hand and then sent this back to anonym’s plate for review. Unless I’m super confident and merge it myself, just like 99% of the Jessie work I’ve been doing so far.

#12 Updated by intrigeri 2015-11-18 07:23:42

  • QA Check changed from Ready for QA to Dev Needed

This branch seems to break emergency shutdown (pulling out the boot USB stick).

#13 Updated by intrigeri 2015-11-19 02:41:08

  • Target version deleted (Tails_2.0)

Not a blocker for 2.0. I’ll treat this as a fun procrastination task.

#14 Updated by intrigeri 2016-06-03 12:16:33

  • Feature Branch changed from feature/wiperam-deb to feature/7468-wiperam-deb

#15 Updated by intrigeri 2016-06-06 05:30:28

intrigeri wrote:
> This branch seems to break emergency shutdown (pulling out the boot USB stick).

It’s still the case: the “Tails shuts down on DVD boot medium removal” automated test fails; emergency shutdown is triggered, but then the system never actually shuts down.

#16 Updated by intrigeri 2017-04-05 17:58:19

  • Status changed from In Progress to Rejected
  • Assignee deleted (intrigeri)
  • QA Check deleted (Dev Needed)

See Bug #12354: we’re dropping our kexec-based implementation, that’s not robust enough, gives poor UX, and a reasonably good alternative is now available.