Project

General

Profile

Bug #8897

The link to persistence documentation in tails-persistence-setup doesn't trigger any user-visible action

Added by intrigeri almost 3 years ago. Updated over 1 year ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Persistence
Target version:
Start date:
02/12/2015
Due date:
% Done:

0%

QA Check:
Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

Tails 1.2.3, logged in with French locales. The link turns from blue to purple, though.


Related issues

Related to Tails - Bug #5466: Link to documentation in Tails Installer does not open the documentation because it points to an old URL which is not properly redirected in Tails Resolved
Related to Tails - Bug #7989: Jessie: raw HTML is displayed in desktop notifications Resolved 10/02/2014 10/15/2015

History

#1 Updated by intrigeri almost 3 years ago

  • Related to Bug #5466: Link to documentation in Tails Installer does not open the documentation because it points to an old URL which is not properly redirected in Tails added

#2 Updated by intrigeri almost 3 years ago

t-p-s runs as its dedicated user. No big surprise it doesn't manage to run the system's default web browser (Tor Browser, defined in /etc/gnome/defaults.list, and in the x-www-browser and gnome-www-browser alternatives).

So far, our options seem to be:

  • switch back to using Yelp as the documentation viewer: needs to fix lots of bugs in it first
  • allow t-p-s to run some web browser (probably with a weird config and behaviour) as it own user
  • create a secure enough facility in Tails, to allow an application running as some user to open a URL in a web browser running as another user; in this case, t-p-s would open the link in the Tor Browser, or in the Unsafe Browser, running as the amnesia user; maybe there's prior work in this area; maybe we'll need something like this at some point; maybe it could "simply" be implemented with polkit rules + pkexec
  • anything else?

#3 Updated by intrigeri over 2 years ago

  • Target version changed from Tails_1.3.2 to Tails_1.4

#4 Updated by intrigeri over 2 years ago

  • Target version changed from Tails_1.4 to Hole in the Roof

This has been broken for too long, and I doubt I'll have time to fix it in time for 1.4 => calling it a Hole in the Roof.

#5 Updated by intrigeri over 2 years ago

  • Related to Bug #7989: Jessie: raw HTML is displayed in desktop notifications added

#6 Updated by BitingBird about 2 years ago

Still the case in Tails Jessie.

#7 Updated by segfault over 1 year ago

I think the link this ticket is about has been removed. I can't see any link in the tails-persistence-setup GUI.

Also, I just tried to start the tor-browser as the tails-persistence-setup user. It gave an error about not being permitted to create "/home/tails-persistence-setup". After creating the home directory, I was able to start the Tor Browser as this user. This only seems to work while the tails-persistence-setup GUI is running.

So maybe we could just create the home directory and put the link back in?

Edit: The Tor Browser run as tails-persistence-setup can't connect to Tor. This (and other problems the different user will cause) might be confusing for users, since the browser window does not look any different than the normal Tor Browser. Maybe we should just leave the link out.

#8 Updated by intrigeri over 1 year ago

segfault wrote:

I think the link this ticket is about has been removed. I can't see any link in the tails-persistence-setup GUI.

There is definitely one when one starts persistence-setup and no persistent volume exists yet: <b>Beware!</b> Using persistence has consequences that must be well understood. Tails can't help you if you use it wrong! See <a href='file:///usr/share/doc/tails/website/doc/first_steps/persistence.en.html'>Tails documentation about persistence</a> to learn more. <- just tested and confirmed.

Also, I just tried to start the tor-browser as the tails-persistence-setup user. It gave an error about not being permitted to create "/home/tails-persistence-setup". After creating the home directory, I was able to start the Tor Browser as this user. This only seems to work while the tails-persistence-setup GUI is running.

So maybe we could just create the home directory and put the link back in?

Edit: The Tor Browser run as tails-persistence-setup can't connect to Tor. This (and other problems the different user will cause) might be confusing for users, since the browser window does not look any different than the normal Tor Browser. Maybe we should just leave the link out.

FTR the link points to file:///, so we don't care if it uses Tor or not. But yeah, firing up a browser (be it the Tor or Unsafe one) as the tails-persistence-setup user is bound to be confusing for users, let's not do that.

Also available in: Atom PDF