Bug #9099

Document that Tails may leave traces in video memory

Added by intrigeri 2015-03-23 16:00:50 . Updated 2015-03-30 23:12:59 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Tails_1.3.2
Start date:
2015-03-23
Due date:
% Done:

100%

Feature Branch:
bitingbird:doc/9099-video_memory
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

See Feature #5356 and in particular the Palinopsia PoC.

Subtasks

Related issues

Related to Tails - Feature #5356: Erase video memory on shutdown Confirmed

History

#1 Updated by intrigeri 2015-03-23 16:01:02

#2 Updated by BitingBird 2015-03-23 20:08:13

  • Assignee set to BitingBird
  • Target version changed from Tails_1.3.2 to Tails_1.4

I’ll see if I put it in the warnings, known issues or something else. In any case, it will not be for 1.3.2, there are already too much things to review for it, but it will be in 1.4.

#3 Updated by intrigeri 2015-03-23 20:14:26

> I’ll see if I put it in the warnings, known issues or something else.

Yay!

> In any case, it will not be for 1.3.2, there are already too much things to review for it, but it will be in 1.4.

I think it’s urgent enough to:

  • either warrant allowing e.g. me to review it initially, and not necessarily sajolida;
  • or, replace another one of your branches that sajolida is meant to review.

#4 Updated by BitingBird 2015-03-27 20:58:47

After reflexion, it doesn’t belong in the warnings, because those are limits of Tails that are going to stay. So I think I’ll add it to the known issues.

#5 Updated by BitingBird 2015-03-27 21:00:26

  • Status changed from Confirmed to In Progress
  • Target version changed from Tails_1.4 to Tails_1.3.2
  • Feature Branch set to bitingbird:doc/9099-video_memory

#6 Updated by BitingBird 2015-03-27 21:32:57

  • Assignee deleted (BitingBird)
  • QA Check set to Ready for QA

Added a section in the known issues, with a link to the ticket. While I was at it, I corrected many things in the known issues page (corrected links to Redmine, added some, consistently placed them after the problem’s description, and removed a fixed issue). Those are in different commits, but in the same branch.

Built, looks good, please review and merge.

#7 Updated by intrigeri 2015-03-28 09:30:20

  • Assignee set to intrigeri

#8 Updated by intrigeri 2015-03-28 09:30:44

  • % Done changed from 0 to 50

#9 Updated by intrigeri 2015-03-29 15:47:32

  • Assignee changed from intrigeri to BitingBird
  • % Done changed from 50 to 60
  • QA Check changed from Ready for QA to Info Needed

I read “As RAM, the VRAM empties itself in minutes after shutdown and all data disappears, so you should shutdown instead if rebooting.” <— reference?

Otherwise, looks good.

#10 Updated by BitingBird 2015-03-29 19:26:27

https://hsmr.cc/palinopsia/ "Mitigation

If you use you computer to access sensitive data, TURN IT OFF after usage, so VRAM is disconnected from power. "

Their attack works when you reboot, not when you start it cold.

I could remove “in minutes” I guess.

#11 Updated by intrigeri 2015-03-30 08:27:23

Applied in changeset commit:22a89580f958b1cba73cc6afa6b9979331db8d61.

#12 Updated by intrigeri 2015-03-30 08:27:23

Applied in changeset commit:fe92c24e6561d35e47aeb26ce1a34d77f89ebcc7.

#13 Updated by intrigeri 2015-03-30 08:27:24

  • Status changed from In Progress to Fix committed
  • % Done changed from 60 to 100

Applied in changeset commit:293778e055fe3031098a8cf26062f3c1e6133034.

#14 Updated by intrigeri 2015-03-30 08:29:21

  • Status changed from Fix committed to Resolved
  • Assignee deleted (BitingBird)
  • QA Check changed from Info Needed to Pass

Merged into master and polished a bit. BitingBird, please have a look at the commits I’ve added on top of yours.

#15 Updated by BitingBird 2015-03-30 23:12:59

Checked, everything is fine :)