summaryrefslogtreecommitdiffstats
path: root/features/torified_gnupg.feature
diff options
context:
space:
mode:
Diffstat (limited to 'features/torified_gnupg.feature')
-rw-r--r--features/torified_gnupg.feature31
1 files changed, 31 insertions, 0 deletions
diff --git a/features/torified_gnupg.feature b/features/torified_gnupg.feature
new file mode 100644
index 00000000..a5820681
--- /dev/null
+++ b/features/torified_gnupg.feature
@@ -0,0 +1,31 @@
+@product
+Feature: Keyserver interaction with GnuPG
+ As a Tails user
+ when I interact with keyservers using various GnuPG tools
+ the configured keyserver must be used
+ and all Internet traffic should flow only through Tor.
+
+ Background:
+ 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 the "10CC5BC7" OpenPGP key is not in the live user's public keyring
+ And I save the state so the background can be restored next scenario
+
+ Scenario: Fetching OpenPGP keys using GnuPG should work and be done over Tor.
+ When I fetch the "10CC5BC7" OpenPGP key using the GnuPG CLI
+ Then GnuPG uses the configured keyserver
+ And the GnuPG fetch is successful
+ And the "10CC5BC7" key is in the live user's public keyring after at most 120 seconds
+ And all Internet traffic has only flowed through Tor
+
+ Scenario: Fetching OpenPGP keys using Seahorse should work and be done over Tor.
+ When I fetch the "10CC5BC7" OpenPGP key using Seahorse
+ Then the "10CC5BC7" key is in the live user's public keyring after at most 120 seconds
+ And all Internet traffic has only flowed through Tor