After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 669247 - Find remote keys function is completely broken
Find remote keys function is completely broken
Status: RESOLVED FIXED
Product: seahorse
Classification: Applications
Component: general
3.2.x
Other Linux
: Normal major
: ---
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2012-02-02 14:48 UTC by Andreas Moog
Modified: 2012-04-11 06:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
No names shown. (26.23 KB, image/png)
2012-02-02 14:48 UTC, Andreas Moog
  Details
Fix remote key search results not showing (1.53 KB, patch)
2012-04-11 06:46 UTC, Robert Ancell
none Details | Review

Description Andreas Moog 2012-02-02 14:48:04 UTC
Created attachment 206639 [details]
No names shown.

The "Find remote keys" functionnality in seahorse is completely broken, rendering it difficult or impossible to add GPG keys into your keyring.

Steps to reproduce:

1- Open Seahorse
2- Select Remote/Find remote keys
3- Type "marc.deslauriers@canonical.com", click search
4- Notice the window shows up empty. Close window.
5- Select Remote/Find remote keys
6- Type "a744be93", click search
7- Notice window finds keys, but the names are missing. (See attached screenshot)
Comment 1 André Klapper 2012-02-02 16:54:38 UTC
If I try this, the statusbar says: "Couldn't communicate with server 'pool.sks-keyservers.net': Cannot resolve hostname."
Comment 2 Andreas Moog 2012-02-02 17:13:30 UTC
"Cannot resolve hostname." - Can you resolve pook.sks-keyservers.net via 'host pool.sks-keyservers.net'?
Comment 3 André Klapper 2012-02-02 17:22:47 UTC
$:andre\> host pool.sks-keyservers.net
pool.sks-keyservers.net has address 64.15.152.44
pool.sks-keyservers.net has address 66.109.111.12
pool.sks-keyservers.net has address 72.9.241.21
pool.sks-keyservers.net has address 78.47.40.248
pool.sks-keyservers.net has address 82.138.79.151
pool.sks-keyservers.net has address 94.174.223.172
pool.sks-keyservers.net has address 130.206.1.8
pool.sks-keyservers.net has address 176.9.51.79
pool.sks-keyservers.net has address 193.151.30.147
pool.sks-keyservers.net has address 195.111.98.30
;; Truncated, retrying in TCP mode.
;; Connection to 10.0.0.1#53(10.0.0.1) for pool.sks-keyservers.net failed: connection refused.

But that's probably a different problem than what this bug report is about. :)
Comment 4 Burkart Lingner 2012-02-17 18:46:06 UTC
I can confirm this bug. When running seahorse from the command line it prints

** Message: invalid keyid (less than 16 chars): A744BE93

upon remote search. Maybe this helps triaging the bug.
Comment 5 Stef Walter 2012-02-29 09:38:11 UTC
Yes, that was pretty broken. However, good news, this was fixed in the 3.3.x releases. I've tried your steps and they do work on git master.

Was fixed by this refactoring and related patches:

commit 0deb6bf417db5a6d6ce9181c897bf1ad212965c5
Author: Stef Walter <stefw@collabora.co.uk>
Date:   Wed Sep 7 13:02:56 2011 +0200

    Refactor core of seahorse
    
     * Objects are owned by sources not by the SeahorseContext
     * No more unique identifiers for objects, since these don't
       fit well with PKCS#11 objects at all.
     * Cleanup SeahorseSource and remove server stuff.
     * All server related stuff goes into the pgp backend.
     * More well defined backends
     * DNS-SD stuff goes into the pgp backend

Please reopen if you can duplicate using the latest seahorse release.
Comment 6 Robert Ancell 2012-04-11 06:46:38 UTC
Created attachment 211809 [details] [review]
Fix remote key search results not showing

It just seems to be the keys that were downloaded weren't "realized" in the code.  This patch seems to fix it and will be shipped in Ubuntu 12.04.  Attaching it here in case anyone else is still using 3.2 and needs the same fix.