summaryrefslogtreecommitdiffstats
path: root/features/tor_bridges.feature
diff options
context:
space:
mode:
Diffstat (limited to 'features/tor_bridges.feature')
-rw-r--r--features/tor_bridges.feature36
1 files changed, 0 insertions, 36 deletions
diff --git a/features/tor_bridges.feature b/features/tor_bridges.feature
deleted file mode 100644
index b5277ca7..00000000
--- a/features/tor_bridges.feature
+++ /dev/null
@@ -1,36 +0,0 @@
-@product @fragile
-Feature: Using Tails with Tor pluggable transports
- As a Tails user
- I want to circumvent censorship of Tor by using Tor pluggable transports
- And avoid connecting directly to the Tor Network
-
- Background:
- Given I have started Tails from DVD without network and logged in with bridge mode enabled
- And I capture all network traffic
- When the network is plugged
- Then the Tor Launcher autostarts
- And the Tor Launcher uses all expected TBB shared libraries
-
- Scenario: Using bridges
- When I configure some Bridge pluggable transports in Tor Launcher
- Then Tor is ready
- And available upgrades have been checked
- And all Internet traffic has only flowed through the configured pluggable transports
-
- Scenario: Using obfs2 pluggable transports
- When I configure some obfs2 pluggable transports in Tor Launcher
- Then Tor is ready
- And available upgrades have been checked
- And all Internet traffic has only flowed through the configured pluggable transports
-
- Scenario: Using obfs3 pluggable transports
- When I configure some obfs3 pluggable transports in Tor Launcher
- Then Tor is ready
- And available upgrades have been checked
- And all Internet traffic has only flowed through the configured pluggable transports
-
- Scenario: Using obfs4 pluggable transports
- When I configure some obfs4 pluggable transports in Tor Launcher
- Then Tor is ready
- And available upgrades have been checked
- And all Internet traffic has only flowed through the configured pluggable transports