Feature #5785

Detect captive portals

Added by Tails 2013-07-18 07:46:15 . Updated 2019-08-07 11:25:41 .

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

0%

Feature Branch:
Type of work:
Research
Blueprint:

https://tails.boum.org/blueprint/detect_captive_portals

Starter:
0
Affected tool:
Deliverable for:

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 handling Confirmed

0

Related issues

Related to Tails - Feature #7437: Consider adding a progress indicator while establishing a connection to Tor Duplicate 2014-06-22
Related to Tails - Feature #10491: Redesign the network configuration and startup Confirmed 2014-06-22
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 2018-06-04
Related to Tails - Feature #12213: Wayland in Tails 5.0 (Bullseye) In Progress 2017-09-02
Has duplicate Tails - Feature #7448: UX: Check whether we might be on a captive portal if Tor fails to connect Duplicate 2014-06-22

History

#1 Updated by intrigeri 2013-09-04 03:27:08

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

#2 Updated by BitingBird 2014-06-09 12:17:03

  • Subject changed from detect captive portals to Detect captive portals

#3 Updated by BitingBird 2014-06-22 01:17:10

  • Description updated

#4 Updated by BitingBird 2014-06-22 01:17:30

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

#5 Updated by BitingBird 2014-06-22 01:19:32

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

#6 Updated by tchou 2014-07-28 18:44:11

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

#7 Updated by sajolida 2015-11-06 05:29:20

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

#8 Updated by intrigeri 2018-06-10 17:06:11

  • 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 2019-08-07 11:19:23

  • 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 2019-08-07 11:19:56

#11 Updated by sajolida 2019-08-07 11:20:45

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

#12 Updated by intrigeri 2019-08-07 11:24:43

> The Unsafe Browser won’t work with Wayland (cf. Feature #12213)

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

#13 Updated by intrigeri 2019-08-07 11:25:41

> 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 :)