Seahorse can't sync keys with keyservers: Request Entity Too Large
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.
#3 Updated by CyrilBrulebois 4 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.
- Feature Branch set to wip/bugfix/17169-seahorse-key-sync+force-all-tests
I grew tired of filtering out this from test suite results, so I've removed the 2 affected scenarios from our test suite on the stable & devel branches (6b7c5e6a5e9ff308286da049d166c28b0f8ba0df) and reverted this to bring them back on the WIP topic branch for this issue (57212d3c4b091aa386e14d581e011611dc4efa10).