Tails

#1 Updated by tchou 2015-05-27 10:36:02

• blocks Feature #9440: Assistant: Clarify the skill level for the command line scenario added

#2 Updated by sajolida 2015-08-15 08:14:06

• Assignee changed from tchou to sajolida

I’ll take this one…

#3 Updated by sajolida 2015-08-15 11:04:34

• QA Check set to Info Needed

Asked u for tips about Tails Installer on the command line.

#4 Updated by sajolida 2015-09-09 05:16:45

• Target version set to Tails_1.7

#5 Updated by sajolida 2015-10-24 06:53:43

• Status changed from Confirmed to In Progress
• Assignee changed from sajolida to tchou
• QA Check changed from Info Needed to Ready for QA

Done in 042c8af. I think the command line part of this scenario should only cover downloading and installing as we don’t have a command line version of Tails Installer.

Also, unfortunately, it seems like we need two different scenarios: one for people having an OpenPGP key and one for people with no OpenPGP key. Because the process and expected output are quite different:

• If people have an OpenPGP key they can certify the Tails signing key with their own, and then trust this in the future.
• If people don’t have an OpenPGP key they should do the verification every time and the output will have a “WARNING: This key is not certified with a trusted signature!”.

We could also choose to support only one kind of scenario. Then I don’t think that we can only support “I don’t have an OpenPGP key” because then this scenario becomes a bit ridiculous for people knowledgable about OpenPGP (and they are clearly in the user base for this scenario). But if we decide to support only “I have an OpenPGP key”, then we’re limiting who can follow this scenario and this extra requirement should be made clear in the router before people start.

tchou, what do you think? I think this is quite urgent to decide as it could impact the router. Note that this discussion is heavily linked with Feature #9440 (assigned to you).

#7 Updated by tchou 2015-10-27 04:28:16

• Assignee changed from tchou to sajolida

Case “I don’t have an OpenPGP key” is “I don’t have an OpenPGP key” and I don’t want to have one. I think we could have just one use case, the “I have an OpenPGP key” and at its beginning, say 2 words about pgp and webpages where people could learn to use it.

#8 Updated by sajolida 2015-10-27 10:13:26

• Status changed from In Progress to Resolved
• Assignee deleted (sajolida)

I’m fine with having instructions only for people who have an OpenPGP key already. Still, as creating an OpenPGP key is clearly outside of the scope of installing Tails, it should be made clear in the router that an OpenPGP key is a requirement for this scenario. If we do this, then it doesn’t make much sense to explain what is OpenPGP at the beginning of the scenario (which means after people saw that they needed an OpenPGP key to follow it).

All this also means that the router should be adapted to make this clear. I created Feature #10433 to track this. Do you mind working on this? I’m a bit overwhelmed right now…

#10 Updated by intrigeri 2018-04-08 16:46:36

• QA Check deleted (Ready for QA)