Commit 68fa3d9d authored by intrigeri's avatar intrigeri
Browse files

Test suite: use hopefully more reliable public GnuPG key (refs: #15771)

So far we were using anonym's key, on the ground that he would maintain
it and worst case, if he fails to keep it up-to-date, notice if automated tests
start failing. This did not work: his key has expired a couple days ago.

So let's switch to dkg's key and hope he'll maintain it better :)

While I'm at it, let's use the full fingerprint instead of a short ID when
feasible (dkg actually has published another key with the same short ID, most
likely for demonstration purposes). But Seahorse does not support fetching keys
by fingerprint so the corresponding steps keep using the short ID and I'm
updating the expected picture to match the non-revoked one of these two keys.
parent cd812efb
features/images/SeahorseFoundKeyResult.png

856 Bytes | W: | H:

features/images/SeahorseFoundKeyResult.png

4.54 KB | W: | H:

features/images/SeahorseFoundKeyResult.png
features/images/SeahorseFoundKeyResult.png
features/images/SeahorseFoundKeyResult.png
features/images/SeahorseFoundKeyResult.png
  • 2-up
  • Swipe
  • Onion skin
......@@ -8,46 +8,46 @@ Feature: Keyserver interaction with GnuPG
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
And the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" OpenPGP key is not in the live user's public keyring
And GnuPG is configured to use Chutney's onion keyserver
And Seahorse is configured to use Chutney's onion 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
When I fetch the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" OpenPGP key using the GnuPG CLI
And the GnuPG fetch is successful
Then the "10CC5BC7" key is in the live user's public keyring
Then the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" key is in the live user's public keyring
And GnuPG's dirmngr uses the configured keyserver
Scenario: Fetching OpenPGP keys using Seahorse should work and be done over Tor.
When I fetch the "10CC5BC7" OpenPGP key using Seahorse
When I fetch the "D21739E9" OpenPGP key using Seahorse
And the Seahorse operation is successful
Then the "10CC5BC7" key is in the live user's public keyring
Then the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" key is in the live user's public keyring
Scenario: Fetching OpenPGP keys using Seahorse via the OpenPGP Applet should work and be done over Tor.
When I fetch the "10CC5BC7" OpenPGP key using Seahorse via the OpenPGP Applet
When I fetch the "D21739E9" OpenPGP key using Seahorse via the OpenPGP Applet
And the Seahorse operation is successful
Then the "10CC5BC7" key is in the live user's public keyring
Then the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" 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
Given I fetch the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" 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
And the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" key is in the live user's public keyring
But the key "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" has only 10 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
Then the key "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" has more than 10 signatures
Scenario: Syncing OpenPGP keys using Seahorse started from the OpenPGP Applet should work and be done over Tor.
Given I fetch the "10CC5BC7" OpenPGP key using the GnuPG CLI without any signatures
Given I fetch the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" 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
And the "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" key is in the live user's public keyring
But the key "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" has only 10 signatures
When I start Seahorse via the 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
Then the key "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9" has more than 10 signatures
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment