Project

General

Profile

Bug #11785

Users get confused by the particularities of the Tails signing key

Added by emmapeel over 3 years ago. Updated over 1 year ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
Installation
Target version:
-
Start date:
09/08/2016
Due date:
% Done:

0%

Feature Branch:
Type of work:
End-user documentation
Blueprint:
Starter:
Affected tool:
Installation Assistant

Description

We receive many support requests about users stuck on the verification process
because several applications cannot cope with the fact that we have an expired subkey or sign with the subkey, etc. Examples are:

  • Seahorse #11622
    Currently can not import the Tails signing key because of this particularity.
    This would be the default graphic way of doing it on Tails.
  • Kleopatra
    Recommended on our website for Windows users, has problems to verify the image.

Explaining the particularities of our signing key on some part of the website would be good, only I don't know where to place it.

Options are:

- Known Issues page
- Download and verify using OpenPGP]


Related issues

Related to Tails - Bug #13184: On /install/download/openpgp/ put a link to /install for users who are not familiar with OpenPGP Resolved 06/27/2017
Related to Tails - Feature #14977: Improve OpenPGP instructions based on Cody's and jaster's feedback Resolved 11/17/2017
Related to Tails - Bug #15710: The Tails signing key is not trusted from within Tails Confirmed 07/04/2018

History

#1 Updated by intrigeri over 3 years ago

  • Category set to Installation
  • Assignee set to emmapeel
  • Affected tool set to Installation Assistant

Meta: either this ticket gets an assignee, or the target version should be dropped.

This feedback is useful to me: it's a pretty good example that helps convincing people like me, that were initially unconvinced by the new preferred download+verification method, that the huge majority of our users should not even be suggested to do an OpenPGP -based verification. We've spent so much time in the past trying to make it doable for them, and now I can see why we gave up. I'm happy if some of us want to resume working on this though :)

#2 Updated by sajolida about 3 years ago

  • Subject changed from Users get confused by the particularities of our key. to Users get confused by the particularities of the Tails signing key

#3 Updated by sajolida about 3 years ago

  • Target version set to Tails_2.7

We only use "Deliverable for" for milestones from grants.

#4 Updated by bertagaz about 3 years ago

  • Target version changed from Tails_2.7 to Tails_2.9.1

#5 Updated by anonym about 3 years ago

  • Target version changed from Tails_2.9.1 to Tails 2.10

#6 Updated by anonym about 3 years ago

  • Target version changed from Tails 2.10 to Tails_2.11

#7 Updated by anonym almost 3 years ago

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

#8 Updated by intrigeri almost 3 years ago

  • Target version deleted (Tails_2.12)

emmapeel, may you please clarify if you want to take care of this?

#9 Updated by emmapeel almost 3 years ago

  • Assignee deleted (emmapeel)

Not really, at least not in the foreseeable future.

#10 Updated by u over 2 years ago

  • Priority changed from Normal to Low

Lowering priority as we hope that most users don't use OpenPGP to verify if they are not familiar with it.

#11 Updated by u over 2 years ago

  • Related to Bug #13184: On /install/download/openpgp/ put a link to /install for users who are not familiar with OpenPGP added

#12 Updated by u about 2 years ago

  • Related to Feature #14977: Improve OpenPGP instructions based on Cody's and jaster's feedback added

#13 Updated by u over 1 year ago

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

I'm rejecting this ticket as it has no assignee, and we want users to verify using the extension instead.

#14 Updated by u over 1 year ago

  • Related to Bug #15710: The Tails signing key is not trusted from within Tails added

Also available in: Atom PDF