torified_gnupg.feature 2.5 KB

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