summaryrefslogtreecommitdiffstats
path: root/wiki/src/blueprint/network_connection.mdwn
diff options
context:
space:
mode:
authorsajolida <sajolida@pimienta.org>2015-11-08 07:20:13 +0000
committersajolida <sajolida@pimienta.org>2015-11-08 07:22:37 +0000
commitb0a7fcf35c034f68f8b134efe0423f96a937da81 (patch)
treeccaefdb9d6b69449541488dd9b3e669a31609fd0 /wiki/src/blueprint/network_connection.mdwn
parente70ea31a7d2cd51a918be72d79535cc0093ef5f4 (diff)
More on the best way to ask for bridges
Diffstat (limited to 'wiki/src/blueprint/network_connection.mdwn')
-rw-r--r--wiki/src/blueprint/network_connection.mdwn9
1 files changed, 8 insertions, 1 deletions
diff --git a/wiki/src/blueprint/network_connection.mdwn b/wiki/src/blueprint/network_connection.mdwn
index 01b29dd..ccf43dc 100644
--- a/wiki/src/blueprint/network_connection.mdwn
+++ b/wiki/src/blueprint/network_connection.mdwn
@@ -47,11 +47,18 @@ Open questions
- 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?
+ - What's the best way of asking for bridges, keeping in mind
+ situations where people might be at risk if they don't use them?
- 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?
+ - if we have persistent network configuration (for example bridges) per
+ local network, then this might conflict (or duplicate) the fact of
+ asking about bridges in the Greeter
+ - bridges might be needed on a give local network but not on
+ another, would it be possible to ask about that *after* selecting
+ the local network?
- Could we, technically speaking, do something more useful about the failure
of MAC spoofing than disabling the interface? in the Greeter? in the session?