1 @product @check_tor_leaks
2 Feature: Tor stream isolation is effective
4 I want my Torified sessions to be sensibly isolated from each other to prevent identity correlation
7 Given I have started Tails from DVD and logged in and the network is connected
9 Scenario: tails-security-check is using the Tails-specific SocksPort
10 When I monitor the network connections of tails-security-check
11 And I re-run tails-security-check
12 Then I see that tails-security-check is properly stream isolated
14 Scenario: htpdate is using the Tails-specific SocksPort
15 When I monitor the network connections of htpdate
17 Then I see that htpdate is properly stream isolated
19 Scenario: tails-upgrade-frontend-wrapper is using the Tails-specific SocksPort
20 When I monitor the network connections of tails-upgrade-frontend-wrapper
21 And I re-run tails-upgrade-frontend-wrapper
22 Then I see that tails-upgrade-frontend-wrapper is properly stream isolated
26 Scenario: The Tor Browser is using the web browser-specific SocksPort
27 When I monitor the network connections of Tor Browser
28 And I start the Tor Browser
29 And the Tor Browser loads the startup page
30 Then I see that Tor Browser is properly stream isolated
33 Scenario: Gobby is using the default SocksPort
34 When I monitor the network connections of Gobby
35 And I start "Gobby" via GNOME Activities Overview
36 And I connect Gobby to "gobby.debian.org"
37 Then I see that Gobby is properly stream isolated
39 Scenario: SSH is using the default SocksPort
40 When I monitor the network connections of SSH
41 And I run "ssh lizard.tails.boum.org" in GNOME Terminal
42 And I see "SSHAuthVerification.png" after at most 60 seconds
43 Then I see that SSH is properly stream isolated
45 Scenario: whois lookups use the default SocksPort
46 When I monitor the network connections of whois
47 And I query the whois directory service for "boum.org"
48 And the whois command is successful
49 Then I see that whois is properly stream isolated
52 Scenario: Explicitly torify-wrapped applications are using the default SocksPort
53 When I monitor the network connections of Gobby
54 And I run "torify /usr/bin/gobby-0.5" in GNOME Terminal
55 And I connect Gobby to "gobby.debian.org"
56 Then I see that Gobby is properly stream isolated
59 Scenario: Explicitly torsocks-wrapped applications are using the default SocksPort
60 When I monitor the network connections of Gobby
61 And I run "torsocks /usr/bin/gobby-0.5" in GNOME Terminal
62 And I connect Gobby to "gobby.debian.org"
63 Then I see that Gobby is properly stream isolated