Project

General

Profile

Bug #7056

In Wheezy t-p-s leaves TailsData mounted

Added by anonym over 5 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Persistence
Target version:
Start date:
04/08/2014
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Yes
Affected tool:

Description

In Wheezy, after creating a persistent partition with t-p-s, the TailsData filesystem remains mounted, and the corresponding LUKS container remains open. This is a regression since Squeeze.

I say "regression" mostly because it makes the automated test suite fail (see commit cdbee93 for a temporary workaround). OTOH I doubt we want this new behaviour any way.


Related issues

Related to Tails - Feature #7062: Adapt the test suite's check for a persistent volume for Wheezy Resolved 04/11/2014

History

#1 Updated by intrigeri over 5 years ago

  • Status changed from New to Confirmed
  • Assignee set to intrigeri
  • Type of work changed from Research to Code
  • Starter changed from No to Yes

I'll take it by default, but if a recent or new contributor feels like doing it, don't hesitate stealing it from me :)

#2 Updated by intrigeri over 5 years ago

  • Status changed from Confirmed to Rejected

anonym wrote:

In Wheezy, after creating a persistent partition with t-p-s, the TailsData filesystem remains mounted, and the corresponding LUKS container remains open.

I've just verified that this also happens on Squeeze, as I suspected: t-p-s takes no action at all to umount / luksClose TailsData.

So, I think this is more about these steps of our test suite accidentally working on Squeeze for some (good or bad) reason, than about a problem in t-p-s itself. So, I'm closing this ticket, and have filed #7062 to address the real problem.

#3 Updated by intrigeri over 5 years ago

  • Related to Feature #7062: Adapt the test suite's check for a persistent volume for Wheezy added

Also available in: Atom PDF