summaryrefslogtreecommitdiffstats
path: root/features/dhcp.feature
blob: c15ae0c10efb9f0756effa477a3f773b49340265 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
@product
Feature: Getting a DHCP lease without leaking too much information
  As a Tails user
  when I connect to a network with a DHCP server
  I should be able to connect to the Internet
  and the hostname should not have been leaked on the network.

  Scenario: Getting a DHCP lease with the default NetworkManager connection
    Given a computer
    And I capture all network traffic
    And I start the computer
    And the computer boots Tails
    And I log in to a new session
    And GNOME has started
    And Tor is ready
    And all notifications have disappeared
    And available upgrades have been checked
    Then the hostname should not have been leaked on the network

  Scenario: Getting a DHCP lease with a manually configured NetworkManager connection
    Given a computer
    And I capture all network traffic
    And I start the computer
    And the computer boots Tails
    And I log in to a new session
    And GNOME has started
    And Tor is ready
    And all notifications have disappeared
    And available upgrades have been checked
    And I add a wired DHCP NetworkManager connection called "manually-added-con"
    And I switch to the "manually-added-con" NetworkManager connection
    Then the hostname should not have been leaked on the network