diff options
| author | Philip Hands <phil@hands.com> | 2016-03-14 15:36:16 +0100 |
|---|---|---|
| committer | Holger Levsen <holger@layer-acht.org> | 2016-04-28 21:52:10 +0200 |
| commit | da080c472fc415b0ce918f4dd4a1ab143bb1bca4 (patch) | |
| tree | bf63179f32f0eda0c2d5796e3e31c18c3c1185cf /features/torified_gnupg.feature | |
| parent | 26a9e8ec2bcae03db4d663d87b44d8708d64fdc2 (diff) | |
| download | jenkins.debian.net-da080c472fc415b0ce918f4dd4a1ab143bb1bca4.tar.xz | |
rough attempt to grab the good cucumber bits from recent tails
Diffstat (limited to 'features/torified_gnupg.feature')
| -rw-r--r-- | features/torified_gnupg.feature | 52 |
1 files changed, 37 insertions, 15 deletions
diff --git a/features/torified_gnupg.feature b/features/torified_gnupg.feature index a5820681..374c7ba3 100644 --- a/features/torified_gnupg.feature +++ b/features/torified_gnupg.feature @@ -1,4 +1,4 @@ -@product +@product @check_tor_leaks @fragile Feature: Keyserver interaction with GnuPG As a Tails user when I interact with keyservers using various GnuPG tools @@ -6,26 +6,48 @@ Feature: Keyserver interaction with GnuPG 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 + Given I have started Tails from DVD and logged in and the network is connected 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: Seahorse is configured to use the correct keyserver + Then Seahorse is configured to use the correct keyserver 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 + And the "10CC5BC7" key is in the live user's public keyring 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 + And the Seahorse operation is successful + Then the "10CC5BC7" key is in the live user's public keyring + + Scenario: Fetching OpenPGP keys using Seahorse via the Tails OpenPGP Applet should work and be done over Tor. + When I fetch the "10CC5BC7" OpenPGP key using Seahorse via the Tails OpenPGP Applet + And the Seahorse operation is successful + Then the "10CC5BC7" key is in the live user's public keyring + + Scenario: Syncing OpenPGP keys using Seahorse should work and be done over Tor. + Given I fetch the "10CC5BC7" OpenPGP key using the GnuPG CLI without any signatures + And the GnuPG fetch is successful + And the "10CC5BC7" key is in the live user's public keyring + But the key "10CC5BC7" has only 2 signatures + When I start Seahorse + Then Seahorse has opened + And I enable key synchronization in Seahorse + And I synchronize keys in Seahorse + And the Seahorse operation is successful + Then the key "10CC5BC7" has more than 2 signatures + + Scenario: Syncing OpenPGP keys using Seahorse started from the Tails OpenPGP Applet should work and be done over Tor. + Given I fetch the "10CC5BC7" OpenPGP key using the GnuPG CLI without any signatures + And the GnuPG fetch is successful + And the "10CC5BC7" key is in the live user's public keyring + But the key "10CC5BC7" has only 2 signatures + When I start Seahorse via the Tails OpenPGP Applet + Then Seahorse has opened + And I enable key synchronization in Seahorse + And I synchronize keys in Seahorse + And the Seahorse operation is successful + Then the key "10CC5BC7" has more than 2 signatures |