summaryrefslogtreecommitdiffstats
path: root/features/dhcp.feature
blob: 18874dbf168b1d5168db7d51810c56233e432bdf (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
@product @fragile
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.

  Background:
    Given I have started Tails from DVD without network and logged in
    And I capture all network traffic
    And the network is plugged
    And Tor is ready
    And all notifications have disappeared
    And available upgrades have been checked

  Scenario: Getting a DHCP lease with the default NetworkManager connection
    Then the hostname should not have been leaked on the network

  Scenario: Getting a DHCP lease with a manually configured NetworkManager connection
    When 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