Project

General

Profile

Feature #5785

Detect captive portals

Added by Tails about 6 years ago. Updated 13 days ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
09/26/2014
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Starter:
No
Affected tool:

Description

This is an outcome of the 1st Tails usability testing session.

it would be nice to have a little message saying "it might be that you're on a captive portal network. you might want to open the unsafe browser to connect to it" if Tor fails to synchronize after some time.


Subtasks

Bug #7950: Consider using GNOME's captive portal handlingConfirmed


Related issues

Related to Tails - Feature #7437: Consider adding a progress indicator while establishing a connection to Tor Duplicate 06/22/2014
Related to Tails - Feature #10491: Redesign the network configuration and startup Confirmed 06/22/2014
Related to Tails - Bug #15635: The Unsafe Browser allows to retrieve the public IP address by a compromised amnesia user with no user interaction Confirmed 06/04/2018
Related to Tails - Feature #12213: Wayland in Tails 5.0 (Bullseye) In Progress 09/02/2017
Duplicated by Tails - Feature #7448: UX: Check whether we might be on a captive portal if Tor fails to connect Duplicate 06/22/2014

History

#1 Updated by intrigeri almost 6 years ago

  • Priority changed from Normal to Low
  • Starter set to No

#2 Updated by BitingBird about 5 years ago

  • Subject changed from detect captive portals to Detect captive portals

#3 Updated by BitingBird about 5 years ago

  • Description updated (diff)

#4 Updated by BitingBird about 5 years ago

  • Duplicated by Feature #7448: UX: Check whether we might be on a captive portal if Tor fails to connect added

#5 Updated by BitingBird about 5 years ago

  • Subject changed from Detect captive portals to Detect captive portals when Tor fails to connect

#6 Updated by tchou about 5 years ago

  • Related to Feature #7437: Consider adding a progress indicator while establishing a connection to Tor added

#7 Updated by sajolida almost 4 years ago

  • Related to Feature #10491: Redesign the network configuration and startup added

#8 Updated by intrigeri about 1 year ago

  • Related to Bug #15635: The Unsafe Browser allows to retrieve the public IP address by a compromised amnesia user with no user interaction added

#9 Updated by sajolida 13 days ago

  • Subject changed from Detect captive portals when Tor fails to connect to Detect captive portals

We should consider detecting captive portals before Tor fails to connect. It's a common feature on smartphones for example, so the network fingerprint of doing this proactively might be acceptable.

#10 Updated by sajolida 13 days ago

#11 Updated by sajolida 13 days ago

The Unsafe Browser won't work with Wayland (cf. #12213) so we'll have to find another solution before Tails 5.0.

#12 Updated by intrigeri 13 days ago

The Unsafe Browser won't work with Wayland (cf. #12213)

Well, it won't work as-is, but #12213 is about fixing this, among other things. Of course, if we fix #5785 first, we won't have to :)

#13 Updated by intrigeri 13 days ago

We should consider detecting captive portals before Tor fails to connect. It's a common feature on smartphones for example, so the network fingerprint of doing this proactively might be acceptable.

This will require some security analysis. I hope the conclusion matches this ideal one :)

Also available in: Atom PDF