Bug #14851

Instructions to backup Tails are wrong in terms of permission

Added by mercedes508 2017-10-14 15:39:44 . Updated 2019-09-03 13:36:37 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Target version:
Tails_3.16
Start date:
2017-10-14
Due date:
% Done:

0%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Got a report from user telling that after applying the final commandline for backuping a persistence, the files are owned by root and thus you can’t access them when booting the persistence of your backup…

I just tried and got a permission denied when trying to access files in my persistent folder.

That user told that “Changing —uid from 1000 (i.e. amnesia) to 0 (i.e. root) in the first part of the find, and only applying the command to the directories that should be owned by amnesia appears to have worked correctly (if slightly long-winded).”

Subtasks

Related issues

Related to Tails - Feature #14605: Improve documentation on "Manually copying your persistent data to a new USB stick" Resolved 2017-09-05
Blocks Tails - Feature #16711: Core work 2019Q3 → 2019Q4: Technical writing Resolved 2016-01-08

History

#1 Updated by sajolida 2017-11-06 10:37:13

  • related to Feature #14605: Improve documentation on "Manually copying your persistent data to a new USB stick" added

#2 Updated by sajolida 2017-11-06 10:37:27

  • blocks Feature #14758: Core work 2017Q4 → 2018Q1: Technical writing added

#3 Updated by sajolida 2018-03-27 11:26:33

  • blocked by deleted (Feature #14758: Core work 2017Q4 → 2018Q1: Technical writing)

#4 Updated by sajolida 2018-03-27 11:26:40

  • blocks Feature #15411: Core work 2018Q2 → 2018Q3: Technical writing added

#5 Updated by sajolida 2018-03-27 11:26:46

I’m out of budget for this quarter.

#6 Updated by sajolida 2018-04-11 13:40:06

  • Assignee changed from sajolida to cbrownstein

Cody: I’m assiging this one to you as part of the big problem space “Persistent storage vs Backups”.
Please check which parts of it are the best to tackle first.

#7 Updated by sajolida 2018-07-26 18:22:44

  • Type of work changed from Contributors documentation to End-user documentation

#8 Updated by sajolida 2018-08-04 10:01:01

  • Assignee changed from cbrownstein to sajolida
  • Target version set to Tails_3.9

Cody: if you don’t mind I’ll take over this problem space for some time since I’ve been working on Bug #15685 lately.

#9 Updated by sajolida 2018-08-13 13:57:59

  • Target version changed from Tails_3.9 to Tails_3.10.1

#10 Updated by sajolida 2018-09-11 17:56:16

  • blocked by deleted (Feature #15411: Core work 2018Q2 → 2018Q3: Technical writing)

#11 Updated by sajolida 2018-09-11 17:56:23

  • blocks Feature #15941: Core work 2018Q4 → 2019Q2: Technical writing added

#12 Updated by sajolida 2018-10-18 17:26:34

  • Target version changed from Tails_3.10.1 to Tails_3.11

#13 Updated by sajolida 2018-12-10 15:51:26

  • Target version changed from Tails_3.11 to Tails_3.12

#14 Updated by sajolida 2019-01-28 18:45:34

  • Target version changed from Tails_3.12 to Tails_3.13

#15 Updated by sajolida 2019-03-15 18:05:41

  • Target version changed from Tails_3.13 to Tails_3.14

#16 Updated by sajolida 2019-05-10 11:14:38

  • Target version deleted (Tails_3.14)

#17 Updated by sajolida 2019-07-18 16:53:38

  • blocked by deleted (Feature #15941: Core work 2018Q4 → 2019Q2: Technical writing)

#18 Updated by sajolida 2019-07-18 16:53:53

  • blocks Feature #16711: Core work 2019Q3 → 2019Q4: Technical writing added

#19 Updated by sajolida 2019-09-03 13:36:37

  • Status changed from Confirmed to Rejected
  • Assignee deleted (sajolida)
  • Target version set to Tails_3.16

This issue won’t be relevant in the new doc from Feature #14605.