Feature #10853

Add SecureDrop workflow to our documentation

Added by emmapeel 2016-01-04 16:39:30 . Updated 2018-01-17 16:11:25 .

Status:
Rejected
Priority:
Normal
Assignee:
emmapeel
Category:
Target version:
Start date:
2016-01-04
Due date:
% Done:

0%

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

https://tails.boum.org/blueprint/securedrop/

Starter:
Affected tool:
Deliverable for:

Description

During the CCC we talked with some users that use SecureDrop.

Their workflow is to download a gpg-encrypted file and open it on an air-gapped Tails device. This device has no Internet but it has the local documentation for Tails.

It would be great for this users to be able to follow the different steps of Secure Drop while offline.

Subtasks

History

#1 Updated by sajolida 2016-01-06 15:12:03

  • Status changed from New to Confirmed
  • QA Check deleted (Info Needed)

Note that we agreed to treat this as an exception. This is not purely documenting Tails, but a related project (SecureDrop), and added to the fact that people need to do this offline, if felt that it was an ok exception to our documentation guidelines.

Still, we should get in touch with the guy we talked to at 32C3 to get him write this doc and not put this on our plate.

This would go in the “Advanced Topics” section.

#2 Updated by intrigeri 2016-01-06 15:39:57

> Still, we should get in touch with the guy we talked to at 32C3 to get him write this doc and not put this on our plate.

Just in case some ticket metadata was forgotten: did anyone volunteer to be the “we” in “we agreed to treat this as an exception”, starting with getting in touch with this guy?

#3 Updated by emmapeel 2016-01-06 15:58:57

  • Assignee set to emmapeel
  • Type of work changed from Discuss to End-user documentation

I am in contact with the person.

I think maybe we can create a blueprint, so we can work easily together?

#4 Updated by sajolida 2016-01-07 15:55:01

  • Blueprint set to https://tails.boum.org/blueprint/securedrop/

Done in https://tails.boum.org/blueprint/securedrop/.

#5 Updated by sajolida 2016-01-07 15:56:49

I think we should also get put the SecureDrop upstream in the loop (and they are friends of our at the Freedom of the Press Foundation). Also: I’m ready to help you with the strategy, broad picture, etc. but I won’t have time to work on this really myself in the coming weeks.

#6 Updated by Anonymous 2018-01-17 15:59:50

  • QA Check set to Info Needed

@emmapeel: are you still volunteering to get in touch with the SecureDrop team about writing this documentation? If not, two years have passed, and we should close this ticket and delete the empty blueprint.

#7 Updated by Anonymous 2018-01-17 16:00:21

#8 Updated by Anonymous 2018-01-17 16:00:26

#9 Updated by Anonymous 2018-01-17 16:02:17

Also they seem to have their own documentation about it which we should probably not duplicate: https://docs.securedrop.org/en/stable/tails_guide.html

#10 Updated by Anonymous 2018-01-17 16:11:25

  • Status changed from Confirmed to Rejected

Rejecting this ticket for now. If anybody wants to work in this, you’re welcome to reopen it.

Regarding the duplication of documentation from SecureDrop, the user had claimed the need to have the docs in Tails because they use the machine without network access - which seems logical.
However, I don’t see how we can maintain such a thing without introducing a delta with their documentation at some point and I also think that we don’t have the resources to maintain this documentation on the long term.
If somebody from their team is interested, and commits to do this work, I’m in favor of reopening this ticket.