Project

General

Profile

Bug #12253

Feature #5688: Tails Server: Self-hosted services behind Tails-powered onion services

Use persistence.conf in Tails Server

Added by segfault over 2 years ago. Updated over 1 year ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
02/18/2017
Due date:
% Done:

0%

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

Description

Currently Tails Server does not use the persistence.conf. Instead, it bind-mounts the files/directories directly, both when the persistence option is enabled and when tails-service --restore is executed. The systemd unit chroot_local-includes/lib/systemd/system/tails-server-persistence.service executes tails-service --restore after boot, to mount the persistent files.

It would be nice if instead we would use the same persistence framework everywhere.


Related issues

Related to Tails - Bug #11533: Add support for bind-mounted files to the live-boot persistence backend In Progress 06/15/2016

Associated revisions

Revision b896d7f7 (diff)
Added by intrigeri over 2 years ago

Drop obolete manual test: the Unsafe Browser has no visible search engine anymore (refs: #12573, #12253).

History

#1 Updated by segfault over 2 years ago

  • Related to Bug #11533: Add support for bind-mounted files to the live-boot persistence backend added

#2 Updated by intrigeri over 2 years ago

  • Status changed from Confirmed to In Progress

#3 Updated by intrigeri over 2 years ago

  • Status changed from In Progress to Confirmed

Ouch, sorry I've mistyped a ticket number and erroneously referenced this one.

#4 Updated by u almost 2 years ago

@segfault, would you like to set a target version for this?

#5 Updated by segfault almost 2 years ago

  • Target version set to Tails_3.9

#6 Updated by segfault almost 2 years ago

  • Parent task set to #5688

#7 Updated by segfault over 1 year ago

  • Target version deleted (Tails_3.9)

Also available in: Atom PDF