Tails

#1 Updated by sajolida 2015-11-24 02:46:25

• Parent task set to Feature #8590

#2 Updated by sajolida 2015-12-10 08:46:42

• Status changed from Confirmed to In Progress
• Assignee changed from sajolida to tchou
• QA Check set to Info Needed
• Feature Branch set to web/10621-expert-command-lines

I did “Use local signature by default [44]” please review.

I can’t work on the rest until Tails Installer gets in Debian (I think it’s in the queue now).

Regarding, “Explain that unverified signatures are fine” I don’t understand what this refers to and I think it was your observation. So can you please send me a gpg output and point me to what needs to be explained.

Because when I do —check-sigs, all the signatures are verified (the ! sign). One line is marked as “[User ID not found]”. What is this about exactly?

#3 Updated by sajolida 2015-12-10 08:46:58

• blocked by Feature #8557: Have Tails Installer uploaded and accepted into Debian added

#4 Updated by tchou 2015-12-12 05:46:54

• Assignee changed from tchou to sajolida
• QA Check deleted (Info Needed)

After gpg --keyid-format 0xlong --check-sigs A490D0F4D311A4153E2BB7CADBB802B258ACD84F

128 signatures non vérifiées à cause de clefs manquantes

#5 Updated by tchou 2015-12-12 05:51:39

• QA Check set to Ready for QA

Maybe talk explicitly about “local signature” in “Certify the Tails signing key with your own key” ?

#6 Updated by sajolida 2015-12-15 04:33:08

• Assignee changed from sajolida to tchou

Regarding the local signature, please review aa92c2c..373a453.

Regarding the unknown signatures, please review 8e3178e.

#7 Updated by tchou 2015-12-15 06:59:47

• Assignee changed from tchou to sajolida
• QA Check changed from Ready for QA to Pass

ok.

I’m fine like it is, but just one little questions (if you don’t have time you can skip it):
- you write “Doing so allows people …” after the command instructions. I wondering what make this kind of explaination go after or before instructions. I would put it before, just wondering.

#8 Updated by sajolida 2015-12-16 08:28:33

• Status changed from In Progress to Resolved
• % Done changed from 0 to 100

Applied in changeset commit:8ca343e8ad3a3f3b55a4127996d29fa252219518.

#9 Updated by sajolida 2015-12-16 08:34:47

• Status changed from Resolved to In Progress
• Target version changed from Tails_1.8 to Tails_2.0
• % Done changed from 100 to 0
• QA Check changed from Pass to Dev Needed

Thanks for pointing this out. I think that both would work. I guess I chose to put the command line before “doing so” to be more to the point in terms of actions and make it easier to have a parallel construction with the first option (—lsign).

I also think that in this context, the “doing so” is more like a tip than a key element that will help people take this decision. Our document is not really the good place to teach people about local and public signature anyway, so I’m being nice without trying to be exhaustive here or annoying people who already know what they want.

So I did a first merge of this. Still, this ticket is blocked by Feature #8557 so I’ll keep it open.

#11 Updated by sajolida 2016-01-03 16:13:36

• related to Feature #8805: Have Tails Installer in Jessie backports added

#12 Updated by sajolida 2016-01-03 16:13:43

• related to deleted (Feature #8805: Have Tails Installer in Jessie backports)

#13 Updated by sajolida 2016-01-03 16:13:51

• blocked by Feature #8805: Have Tails Installer in Jessie backports added

#14 Updated by sajolida 2016-01-05 17:42:12

• Parent task changed from Feature #8590 to Feature #8592

#15 Updated by sajolida 2016-01-21 20:32:56

• Priority changed from Normal to Elevated

#16 Updated by sajolida 2016-01-22 19:16:43

• Assignee changed from sajolida to tchou
• QA Check changed from Dev Needed to Ready for QA

Worked on the remaining things in d77f7e6..180a613.

I based my work on web/10953-installer-in-backports because I needed stuff in there to prevent nasty conflicts. So you should review Bug #10953 first.

#17 Updated by tchou 2016-01-24 13:37:38

• Assignee changed from tchou to sajolida
• QA Check changed from Ready for QA to Pass

#18 Updated by sajolida 2016-01-24 15:47:12

• Status changed from In Progress to Resolved
• % Done changed from 0 to 100

Applied in changeset commit:c96177e6d60e70a5d46d11a40804cea1efc3807c.

#19 Updated by sajolida 2016-01-24 15:48:36

• Assignee deleted (sajolida)
• % Done changed from 100 to 0
• QA Check deleted (Pass)