2 @product @check_tor_leaks @fragile
3 Feature: Keyserver interaction with GnuPG
5 when I interact with keyservers using various GnuPG tools
6 the configured keyserver must be used
7 and all Internet traffic should flow only through Tor.
10 Given I have started Tails from DVD and logged in and the network is connected
11 And the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" OpenPGP key is not in the live user's public keyring
12 And GnuPG is configured to use Chutney's onion keyserver
13 And Seahorse is configured to use Chutney's onion keyserver
15 Scenario: Fetching OpenPGP keys using GnuPG should work and be done over Tor.
16 When I fetch the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" OpenPGP key using the GnuPG CLI
17 And the GnuPG fetch is successful
18 Then the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" key is in the live user's public keyring
19 And GnuPG's dirmngr uses the configured keyserver
21 Scenario: Fetching OpenPGP keys using Seahorse should work and be done over Tor.
22 When I fetch the "D21739E9" OpenPGP key using Seahorse
23 And the Seahorse operation is successful
24 Then the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" key is in the live user's public keyring
26 Scenario: Fetching OpenPGP keys using Seahorse via the OpenPGP Applet should work and be done over Tor.
27 When I fetch the "D21739E9" OpenPGP key using Seahorse via the OpenPGP Applet
28 And the Seahorse operation is successful
29 Then the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" key is in the live user's public keyring
31 Scenario: Syncing OpenPGP keys using Seahorse should work and be done over Tor.
32 Given I fetch the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" OpenPGP key using the GnuPG CLI without any signatures
33 And the GnuPG fetch is successful
34 And the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" key is in the live user's public keyring
35 But the key "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" has less than 42 signatures
37 Then Seahorse has opened
38 And I enable key synchronization in Seahorse
39 And I synchronize keys in Seahorse
40 And the Seahorse operation is successful
41 Then the key "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" has more than 42 signatures
43 Scenario: Syncing OpenPGP keys using Seahorse started from the OpenPGP Applet should work and be done over Tor.
44 Given I fetch the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" OpenPGP key using the GnuPG CLI without any signatures
45 And the GnuPG fetch is successful
46 And the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" key is in the live user's public keyring
47 But the key "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" has less than 42 signatures
48 When I start Seahorse via the OpenPGP Applet
49 Then Seahorse has opened
50 And I enable key synchronization in Seahorse
51 And I synchronize keys in Seahorse
52 And the Seahorse operation is successful
53 Then the key "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" has more than 42 signatures