summaryrefslogtreecommitdiffstats
path: root/features/tor_enforcement.feature
diff options
context:
space:
mode:
authorbertagaz <bertagaz@ptitcanardnoir.org>2016-08-07 18:43:02 +0200
committerbertagaz <bertagaz@ptitcanardnoir.org>2016-08-07 18:43:02 +0200
commit74f0d7d8c8480a2d3d6435aafabec59bc52c7fca (patch)
treedb5221325946d612431ac343568abd8ce17d1524 /features/tor_enforcement.feature
parentb6e73e0facf77b1000ef0cfe31fc86f79072b575 (diff)
parent76781166535d1cffc3601c95fb91361fd335d0a0 (diff)
Merge remote-tracking branch 'origin/devel' into feature/tor-bootstrap-failure-stats-for-10238feature/tor-bootstrap-failure-stats-for-10238
Diffstat (limited to 'features/tor_enforcement.feature')
-rw-r--r--features/tor_enforcement.feature4
1 files changed, 0 insertions, 4 deletions
diff --git a/features/tor_enforcement.feature b/features/tor_enforcement.feature
index a958b14..fd4acef 100644
--- a/features/tor_enforcement.feature
+++ b/features/tor_enforcement.feature
@@ -5,10 +5,6 @@ Feature: The Tor enforcement is effective
And as a Tails developer
I want to ensure that the automated test suite detects firewall leaks reliably
- Scenario: Tails' Tor binary is configured to use the expected Tor authorities
- Given I have started Tails from DVD and logged in and the network is connected
- Then the Tor binary is configured to use the expected Tor authorities
-
Scenario: The firewall configuration is very restrictive
Given I have started Tails from DVD and logged in and the network is connected
Then the firewall's policy is to drop all IPv4 traffic