blob: 374c7ba308a514830797492a12af3039f548d758 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
@product @check_tor_leaks @fragile
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 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
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
Scenario: Fetching OpenPGP keys using Seahorse should work and be done over Tor.
When I fetch the "10CC5BC7" OpenPGP key using Seahorse
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
|