Feature #17579

Fake, harmless Persistence with another Password ?

Added by 77.97.105.108 2020-04-01 18:31:43 . Updated 2020-04-02 07:47:03 .

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
Persistence
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

In object protection and security branch, its normal to have 2 codes to unlock the safe:
first code to open,
second code to open with an silent alarm for police/armed help.

Whats my story behind ?

When a gov confiscated my USB-Stick because using tails is forbidden in that state, and the Agents torture me to get the passwort to the critical persistence, it would be great to have a password for my real persistence and a second passwort for a fake persistence with a CV, some pictures or something else harmless stuff, to disguise the real persistence with critcal documents.

The GOV free me because they dont think, im harmless and i can go on with uncensored reporting or whatever.

Did u guys understand what my issue/suggestion is and is that technically feasible to make 2 (a harmless and a critical) persistences, selectable via the Passwort ?

Subtasks

Related issues

Is duplicate of Tails - Feature #5929: Consider creating a persistence by default for plausible deniability Confirmed 2016-08-20

History

#1 Updated by intrigeri 2020-04-02 07:46:16

  • is duplicate of Feature #5929: Consider creating a persistence by default for plausible deniability added

#2 Updated by intrigeri 2020-04-02 07:47:03

  • Status changed from New to Duplicate
  • Type of work changed from Security Audit to Research

I understand the goal here is the same as on Feature #5929, so I’m closing this as a duplicate — even though the exact technical solution is different.