Feature #9530

Consider using hkp://ha.pool.sks-keyservers.net in non-hkps-enabled software

Added by intrigeri 2015-06-04 09:16:28 . Updated 2015-09-16 12:25:07 .

Status:
Resolved
Priority:
Low
Assignee:
Category:
Test suite
Target version:
Tails_1.6
Start date:
2015-06-04
Due date:
% Done:

100%

Feature Branch:
Type of work:
Test
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

That’s “a high-availibility subset of the pool that require all servers to be identified as a clustered setup”, according to https://sks-keyservers.net/overview-of-pools.php. Shall we use it for e.g. Seahorse to improve robustness (both for users and the test suite, see e.g. Feature #9518)? (Presumably for hkps-enabled software, we want to keep on using hkps://hkps.pool.sks-keyservers.net). Note that on https://sks-keyservers.net/status/, I see that there are only 4 “servers” (presumably, “clusters”) in that pool.

Subtasks

Related issues

Related to Tails - Bug #9346: Test if switching to a more stable OpenPGP key server improves the Seahorse tests Resolved 2015-05-05

History

#1 Updated by intrigeri 2015-06-04 21:32:00

  • related to Bug #9346: Test if switching to a more stable OpenPGP key server improves the Seahorse tests added

#2 Updated by Dr_Whax 2015-07-06 12:21:10

  • Priority changed from Normal to Low
  • Type of work changed from Discuss to Test

Try using that “HA” pool in the automated test suite after reverting Feature #9518, and measure if it improves things compared to the regular hkps pool.

#3 Updated by intrigeri 2015-07-06 13:38:42

  • Category set to Test suite

#4 Updated by intrigeri 2015-07-07 00:37:36

> Try using that “HA” pool in the automated test suite after reverting Feature #9518, and measure if it improves things compared to the regular hkps pool.

(As per monthly meeting.)

#5 Updated by anonym 2015-09-14 07:09:03

I tried this pool (in the automated test suite, without robustness improvements reverted), and it wasn’t super reliable. I still got some instances of "gpg: no valid OpenPGP data found@ which I suspect gpg may throw sometimes when it actually fails to connect, which seems like a bug. Any way, switching to these doesn’t look like an improvement.

#6 Updated by anonym 2015-09-16 12:25:07

  • Status changed from Confirmed to Resolved
  • Target version set to Tails_1.6
  • % Done changed from 0 to 100

I tested a bit more, and it indeed seems like Tor is the only issue. For instance, with Tor I sometimes get gpg: no valid OpenPGP data found, but I never get it myself when not using Tor. => Closing.