summaryrefslogtreecommitdiffstats
path: root/features/dhcp.feature
diff options
context:
space:
mode:
authorTails developers <amnesia@boum.org>2014-12-19 00:40:08 +0100
committerHolger Levsen <holger@layer-acht.org>2014-12-21 09:45:40 +0100
commit51680b6ebb645d37ebdfcd122ca163b3a638aefa (patch)
tree337e128d2eac3cbc89ecbacf38851bfa33469cd5 /features/dhcp.feature
parent44bab3c86ca3d95837f4c50cc535206352385a46 (diff)
downloadjenkins.debian.net-51680b6ebb645d37ebdfcd122ca163b3a638aefa.tar.xz
files copied from https://git-tails.immerda.ch/tails - many thanks to the tails developers for their nice work and documentation of it - these files have been released under the GNU General Public License version 3 or (at your option) any later version
features/images has been omitted
Diffstat (limited to 'features/dhcp.feature')
-rw-r--r--features/dhcp.feature32
1 files changed, 32 insertions, 0 deletions
diff --git a/features/dhcp.feature b/features/dhcp.feature
new file mode 100644
index 00000000..c15ae0c1
--- /dev/null
+++ b/features/dhcp.feature
@@ -0,0 +1,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