Feature #8260

Check if we need to keep memlockd running longer

Added by intrigeri 2014-11-13 22:16:14 . Updated 2015-11-10 11:52:54 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_2.0
Start date:
2014-11-13
Due date:
% Done:

100%

Feature Branch:
Type of work:
Test
Blueprint:

Starter:
Affected tool:
Deliverable for:
269

Description

Our previous usage of sendsigs.omit.d to prevent sysvinit from killing memlockd on shutdown doesn’t work with systemd. We should evaluate if it’s worth keeping memlockd running a few more seconds, and if it is, then we should find a way to keep it around as late as possible.

If we do need to keep it around, http://www.freedesktop.org/wiki/Software/systemd/RootStorageDaemons/ should be a good starting point.

Subtasks

History

#1 Updated by intrigeri 2015-03-10 00:40:15

  • Subject changed from Keep memlockd running as late as needed when running under systemd to Check if we need to keep memlockd running longer
  • Description updated
  • Type of work changed from Research to Test

In my VMs, I’ve never seen memory erasure fail on Tails/Jessie due to memlockd not living long enough. Next step is to test this on various bare metal hardware, and see if there’s actually a problem to solve.

#2 Updated by intrigeri 2015-07-08 05:29:00

Unparenting, so I can close the parent ticket. This is a follow-up.

#3 Updated by intrigeri 2015-07-13 03:59:00

  • Target version changed from Sustainability_M1 to Tails_2.0

#4 Updated by intrigeri 2015-11-10 11:52:54

  • Status changed from Confirmed to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 0 to 100
  • Deliverable for set to 269

intrigeri wrote:
> In my VMs, I’ve never seen memory erasure fail on Tails/Jessie due to memlockd not living long enough. Next step is to test this on various bare metal hardware, and see if there’s actually a problem to solve.

I’ve tested on a few machines and have not seen issues.

#5 Updated by intrigeri 2015-11-10 11:59:08

  • blocks #8668 added