summaryrefslogtreecommitdiffstats
path: root/wiki/src/blueprint/network_connection.mdwn
diff options
context:
space:
mode:
authorsajolida <sajolida@pimienta.org>2015-11-06 14:14:31 +0000
committersajolida <sajolida@pimienta.org>2015-11-06 14:14:31 +0000
commit2a5814601453726623dfccf03ee6d52751bc6d18 (patch)
tree4c84e725e304d1bd9e239f5b0c4daeb4b3ebcf3c /wiki/src/blueprint/network_connection.mdwn
parent486d442b30c7b485675daaac6182320f90f552d1 (diff)
Start blueprint on network connection configuration and startup
Diffstat (limited to 'wiki/src/blueprint/network_connection.mdwn')
-rw-r--r--wiki/src/blueprint/network_connection.mdwn68
1 files changed, 68 insertions, 0 deletions
diff --git a/wiki/src/blueprint/network_connection.mdwn b/wiki/src/blueprint/network_connection.mdwn
new file mode 100644
index 0000000..01b29dd
--- /dev/null
+++ b/wiki/src/blueprint/network_connection.mdwn
@@ -0,0 +1,68 @@
+[[!meta title="Network connection (configuration and startup)"]]
+
+This is about [[!tails_ticket 10491]].
+
+ - Original post-its by Lunar:
+
+ <a href="https://labs.riseup.net/code/attachments/download/1036/20151002-lunar.jpg"><img src="https://labs.riseup.net/code/attachments/download/1036/20151002-lunar.jpg" width="300px"></a>
+
+ <https://mailman.boum.org/pipermail/tails-dev/2015-October/009593.html>
+
+ - Digital rewrite by SpencerOne:
+
+ <a href="https://labs.riseup.net/code/attachments/download/1035/20151005-spencer.png"><img src="https://labs.riseup.net/code/attachments/download/1035/20151005-spencer.png" width="300px"></a>
+
+Current issues in Tails
+=======================
+
+ - After Tails Greeter, it might be hard for some people to understand where
+ to click on the GNOME desktop to connect a Wi-Fi network.
+
+ - It's not possible to go from direct Tor connection to bridge mode in case
+ you realize once in the session that you actually need them to connect.
+
+ - It's hard to know whether you need to log in through a captive portal.
+
+ - There's no way of triggering Tor to reconnect after logging in through a
+ captive portal.
+
+ - Configuring bridges is done in two steps: (1) activate in the Greeter and
+ (2) configure in Tor Launcher. It can be scary for people who cannot afford
+ connecting without bridges to postponed the configuration after the session
+ is started.
+
+ - Bridges, firewall and proxy have to be configured again each time.
+
+ - There is no visual feedback on whether the connection to Tor is making
+ progress.
+
+ - If MAC spoofing fails but I decide that it's OK not to spoof MAC in my
+ situation, then I have to reboot Tails all the way.
+
+Open questions
+==============
+
+ - What's left from this configuration process on the desktop after Tor is
+ started?
+ - What do we do with the NetworkManager applet?
+ - Do we allow changing or visualizing the current settings?
+
+ - What's the best UX for people in danger if they don't use bridges?
+ - Lunar's proposal: Say you're at risk in the Greeter, then configure
+ bridges in the session.
+ - other possibility: Do everything in the session (offline mode and MAC
+ spoofing could still be optional settings in the Greeter), if so how?
+
+ - Could we, technically speaking, do something more useful about the failure
+ of MAC spoofing than disabling the interface? in the Greeter? in the session?
+ - Should we ask for confirmation before disabling the interface?
+
+ - How shall we integrate the captive portal browser on the desktop in case we
+ need to get back to it (to log in again, to log out)?
+ - Lunar's proposal: as a detached windows
+ - other possibility: invisible browser by default, can be displayed again somehow
+
+Related work
+============
+
+ - [[Captive portal detection|detect_captive_portals]]