Project

General

Profile

Bug #17371

Seahorse - can't connect to keyserver

Added by numbat 2 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

When trying to do anything related to connecting to a keyserver (update/upload/etc), we get this:

Couldn't communicate with server:
"zkaan2xfbuxia2wpf7ofnkbz6r5zdbbvxbunvp5g2iebopbfc4iqmbad.onion" 
Bad Request

A user reported this, I double checked.

I also added other key servers (with or without .onion domains) and had the same errors.

using `gpg` works, even with the keyserver configured in Seahorse:


gpg --keyserver hkp://zkaan2xfbuxia2wpf7ofnkbz6r5zdbbvxbunvp5g2iebopbfc4iqmbad.onion

Screenshots are provided by the user who notified us about the issue.

screenshot1.gif View (108 KB) numbat, 12/23/2019 12:46 PM

screenshot2.gif View (113 KB) numbat, 12/23/2019 12:46 PM


Related issues

Duplicated by Tails - Bug #17482: "Passwords and Keys": Remote keyserver not reachable Duplicate

History

#1 Updated by intrigeri about 2 months ago

When trying to do anything related to connecting to a keyserver (update/upload/etc), we get this:

OK, this ticket has a pretty broad scope, and quite possibly not all of the problems it's about share the same root causes.
I think there are at least 3 different problems here:

1. Wrt. "Sync and Publish Keys"

Known issue, tracked as #17169; I've just reproduced it. The "Bad Request" dialog appears on top of another one ("Request Entity Too Large"). This covers the "update/upload" part of your report, so case closed here ⇒ see you on #17169 :)

2. Wrt. "Find Remote Keys"

2.1. If the keyserver has the key I'm searching for

In my test VM, it seems that Seahorse managed to communicate with the keyserver. But I see an empty list in the result window and these errors in the Journal:

seahorse[8200]: gtk_builder_get_object: assertion 'name != NULL' failed
seahorse[8200]: catalog.vala:61: no place holder found for: (null)

2.2. If I'm searching for a key that is not on keys.openpgp.org (aka. zkaan2xfbuxia2wpf7ofnkbz6r5zdbbvxbunvp5g2iebopbfc4iqmbad.onion)

I get a "Bad Request" error dialog. I think that Seahorse actually managed to connect to the keyserver but it's unable to understand that the reply means "no matching key, sorry". I don't know if that's a bug in Seahorse itself or in how the keyserver communicates results to Seahorse.

Are we on the same page?
Is there any other problem?

#2 Updated by intrigeri about 2 months ago

  • Status changed from New to Confirmed

#3 Updated by intrigeri 5 days ago

  • Duplicated by Bug #17482: "Passwords and Keys": Remote keyserver not reachable added

Also available in: Atom PDF