Project

General

Profile

Bug #17169

Seahorse can't sync keys with keyservers: Request Entity Too Large

Added by intrigeri 3 months ago. Updated about 2 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:

Description

Spotted by our test suite while working on #12689. That's the case:

  • with keys.openpgp.org's Onion service (that my branch for #12689 sets as the default)
  • in our test suite, when using keys.mayfirst.org as the backend

I can't trivially reproduce this with hkp://jirk5u4osbsr34t5.onion but I think it depends on the keyserver that the pool will give us: as the keys.mayfirst.org issue shows, this problem is not specific to keys.openpgp.org.


Related issues

Related to Tails - Bug #12689: gpg --recv-key often hangs due to unreliable keyserver Resolved 06/13/2017
Related to Tails - Bug #14770: "Fetching OpenPGP keys" scenarios are fragile: communication failure with keyserver Resolved 10/04/2017

History

#1 Updated by intrigeri 3 months ago

  • Related to Bug #12689: gpg --recv-key often hangs due to unreliable keyserver added

#2 Updated by intrigeri 3 months ago

  • Related to Bug #14770: "Fetching OpenPGP keys" scenarios are fragile: communication failure with keyserver added

#3 Updated by CyrilBrulebois about 2 months ago

As a data point (since it seems both our settings in the live environment and our test suite settings were updated, if I assembled the changelog correctly): still happening in the automated test suite for 4.1. Since that's not a new issue, not considering that as a blocker, or as a bug to be documented.

features/torified_gnupg.feature:32 # Scenario: Syncing OpenPGP keys using Seahorse should work and be done over Tor.
features/torified_gnupg.feature:48 # Scenario: Syncing OpenPGP keys using Seahorse started from the OpenPGP Applet should work and be done over Tor.

Also available in: Atom PDF