Feature #11256

Replace "Debian Live user" with a more descriptive full user name

Added by sajolida 2016-03-17 16:28:26 . Updated 2016-11-28 18:50:33 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails 2.10
Start date:
2016-03-17
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

When locking the screen, the full name of the amnesia user appears: “Debian Live user”. We could have something nicer. Maybe “amnesia”, maybe “Tails”.

But does this have to reuse the same name as the one we would choose for Feature #5655, for anonymity reasons? or can we use something specific for Tails?

Subtasks

Related issues

Related to Tails - Feature #5655: Share username and hostname amongst all anonymity distributions Confirmed 2016-03-17

History

#1 Updated by sajolida 2016-03-17 16:29:38

  • Assignee set to intrigeri
  • QA Check set to Info Needed

Assigning to intrigeri who’s assignee for Feature #5655 to have a first opinion on whether we should wait for Feature #5655 to use the same display name or if we can find something specific to Tails.

#2 Updated by intrigeri 2016-03-17 19:11:37

  • Assignee changed from intrigeri to sajolida

(There’s been a misunderstanding: I was assigned to Feature #5655 only to do Feature #5655#note-11, in order to kill a pending thread frmo my mailmox; I’ve completed it but forgot to deassign myself. I don’t want to add a new task related to that topic on my plate now, since my plan was to drop one.)

#3 Updated by intrigeri 2016-03-17 19:17:30

  • related to Feature #5655: Share username and hostname amongst all anonymity distributions added

#4 Updated by sajolida 2016-03-18 15:01:17

  • Assignee deleted (sajolida)
  • QA Check deleted (Info Needed)

#5 Updated by intrigeri 2016-07-30 08:50:18

  • Type of work changed from Discuss to Research

(I see security questions that need to be researched, and nothing that’s ready to be discussed.)

#6 Updated by sajolida 2016-09-02 07:25:54

  • Assignee set to segfault
  • Parent task set to Feature #5878
  • Type of work changed from Research to Code

I think that this should be part of Feature #5878 because Feature #5878 will make the screen locker visible to most users (so far it’s available but hidden).

segfault: what do you think?

Regarding which full name to choose, I would put “amnesia” which is the current login and is already refered to in several places in the documentation. This way no more research or discussion are needed and we can jump straight to code.

#7 Updated by segfault 2016-09-02 08:04:06

  • Assignee changed from segfault to anonym
  • QA Check set to Ready for QA

I just pushed a commit to the feature branch of Feature #5684 which removes this “Debian Live user” comment from the amnesia account.
See https://gitlab.com/segfault_/tails.git feature/5684-screen-locker

#8 Updated by sajolida 2016-09-04 02:01:45

  • Target version set to Tails_2.6

Marking this for 2.6 until the status of this is clarified, see Feature #5878#note-16.

#9 Updated by intrigeri 2016-09-09 14:48:01

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

(See Feature #5684#note-54 and Feature #5684#note-55.)

#10 Updated by anonym 2016-11-25 13:26:14

  • Target version changed from Tails_2.9.1 to Tails 2.10

Bumping this feature to the new next major release (given 2.8 was cancelled).

#11 Updated by anonym 2016-11-28 18:08:11

I’ve pushed two commit to our repo’s version of the branch:

d52d946 Enter a name into the Icedove account configuration.
19fb574 Make GNOME's default Lock Screen keyboard shortcut use our locker.


Please review’n’merge, segfault! :)

Edit: I meant to post this to Feature #5684, so please post any follow-ups there.

#12 Updated by anonym 2016-11-28 18:50:33

  • Status changed from Confirmed to Resolved
  • Assignee deleted (anonym)
  • % Done changed from 0 to 100
  • QA Check changed from Ready for QA to Pass