tor_enforcement.feature 3.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172
  1. @product
  2. Feature: The Tor enforcement is effective
  3. As a Tails user
  4. I want all direct Internet connections I do by mistake or applications do by misconfiguration or buggy leaks to be blocked
  5. And as a Tails developer
  6. I want to ensure that the automated test suite detects firewall leaks reliably
  7. Scenario: The firewall configuration is very restrictive
  8. Given I have started Tails from DVD and logged in and the network is connected
  9. Then the firewall's policy is to drop all IPv4 traffic
  10. And the firewall is configured to only allow the clearnet and debian-tor users to connect directly to the Internet over IPv4
  11. And the firewall's NAT rules only redirect traffic for Tor's TransPort and DNSPort
  12. And the firewall is configured to block all external IPv6 traffic
  13. @fragile
  14. Scenario: Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector
  15. Given I have started Tails from DVD and logged in and the network is connected
  16. And I capture all network traffic
  17. When I successfully start the Unsafe Browser
  18. And I open Tails homepage in the Unsafe Browser
  19. And Tails homepage loads in the Unsafe Browser
  20. Then the firewall leak detector has detected leaks
  21. Scenario: Anti test: Detecting TCP leaks of DNS lookups with the firewall leak detector
  22. Given I have started Tails from DVD and logged in and the network is connected
  23. And I capture all network traffic
  24. And I disable Tails' firewall
  25. When I do a TCP DNS lookup of "torproject.org"
  26. Then the firewall leak detector has detected leaks
  27. Scenario: Anti test: Detecting UDP leaks of DNS lookups with the firewall leak detector
  28. Given I have started Tails from DVD and logged in and the network is connected
  29. And I capture all network traffic
  30. And I disable Tails' firewall
  31. When I do a UDP DNS lookup of "torproject.org"
  32. Then the firewall leak detector has detected leaks
  33. Scenario: Anti test: Detecting ICMP leaks of ping with the firewall leak detector
  34. Given I have started Tails from DVD and logged in and the network is connected
  35. And I capture all network traffic
  36. And I disable Tails' firewall
  37. When I send some ICMP pings
  38. Then the firewall leak detector has detected leaks
  39. @check_tor_leaks
  40. Scenario: The Tor enforcement is effective at blocking untorified TCP connection attempts
  41. Given I have started Tails from DVD and logged in and the network is connected
  42. When I open an untorified TCP connections to 1.2.3.4 on port 42 that is expected to fail
  43. Then the untorified connection fails
  44. And the untorified connection is logged as dropped by the firewall
  45. @check_tor_leaks
  46. Scenario: The Tor enforcement is effective at blocking untorified UDP connection attempts
  47. Given I have started Tails from DVD and logged in and the network is connected
  48. When I open an untorified UDP connections to 1.2.3.4 on port 42 that is expected to fail
  49. Then the untorified connection fails
  50. And the untorified connection is logged as dropped by the firewall
  51. @check_tor_leaks @fragile
  52. Scenario: The Tor enforcement is effective at blocking untorified ICMP connection attempts
  53. Given I have started Tails from DVD and logged in and the network is connected
  54. When I open an untorified ICMP connections to 1.2.3.4 that is expected to fail
  55. Then the untorified connection fails
  56. And the untorified connection is logged as dropped by the firewall
  57. Scenario: The system DNS is always set up to use Tor's DNSPort
  58. Given I have started Tails from DVD without network and logged in
  59. And the system DNS is using the local DNS resolver
  60. And the network is plugged
  61. And Tor is ready
  62. Then the system DNS is still using the local DNS resolver