Project

General

Profile

Bug #7051

Seahorse does have a configured default keyserver but it's not selected by default

Added by sajolida over 5 years ago. Updated about 2 years ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
04/09/2014
Due date:
% Done:

0%

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

Description

At least since Tails 0.20, the synchronization of public keys through keyserver is impossible using Seahorse.

To reproduce that:

1. Open Seahorse from "System" → "Preferences" → "Passwords and Encryption Keys".
2. Choose "Remote" → "Sync and Publish Keys".
3. The "Sync" button is deactivated and greyed out.

We should investigate why this is happening.

tails-0.7.2-seahorse.png View (26.5 KB) kytv, 02/25/2015 06:04 PM


Related issues

Related to Tails - Bug #6394: Seahorse launched from the gpgApplet cannot search for public keys Resolved 10/31/2013

History

#1 Updated by intrigeri over 5 years ago

  • Priority changed from Normal to Elevated

Bumping priority, assuming that's a regression.

#2 Updated by sajolida over 5 years ago

I could reproduce this with Tails 0.16 as well which is more than one year old. And to my knowledge, this was the first time to issue was reported. So technically speaking it's a regression but it's a very old one and nobody really noticed in more than one year...

And also, we've had several usability regression regarding keyservers in the past I think, so maybe having a quick test in the manual test suite would help detecting them a big faster :)

#3 Updated by intrigeri over 5 years ago

  • Priority changed from Elevated to Normal

sajolida wrote:

I could reproduce this with Tails 0.16 as well which is more than one year old. And to my knowledge, this was the first time to issue was reported. So technically speaking it's a regression but it's a very old one and nobody really noticed in more than one year...

OK, downgrading priority accordingly.

And also, we've had several usability regression regarding keyservers in the past I think, so maybe having a quick test in the manual test suite would help detecting them a big faster :)

Added to the test suite.

#4 Updated by intrigeri over 5 years ago

Actually, this works just fine in 1.0~rc1, with one manual configuration step: Remote -> Sync and publish keys -> Key servers -> Select the hkp:// server in "Publish keys to" -> Close -> Sync.

So, the question is: what would be the downside of making this configuration the default? Would Seahorse automatically publish all known public keys to this keyserver (which we don't want)?

#5 Updated by intrigeri over 5 years ago

  • Related to Bug #6394: Seahorse launched from the gpgApplet cannot search for public keys added

#6 Updated by sajolida about 5 years ago

This workaround works in Seahorse started from Applications → System Tools → Preferences → Passwords and Keys, but not from Seahorse started from Tails OpenPGP Applet → Manage Keys.

#7 Updated by emmapeel about 5 years ago

more user input fresh from today:

double checked in Tails 1.1 :

  • in Seahorse started from Applications → System Tools → Preferences →
    Passwords and Keys it just wourks out of the box, without even the
    workaround :D
  • Seahorse started from Tails OpenPGP Applet → Manage Keys
    it just doesn't work

#8 Updated by intrigeri about 5 years ago

  • in Seahorse started from Applications → System Tools → Preferences → Passwords and Keys it just wourks out of the box, without even the workaround :D
  • Seahorse started from Tails OpenPGP Applet → Manage Keys it just doesn't work

We're patching seahorse.desktop to start it with torsocks. gpgApplet should probably do the same. That's a very simple coding task, any taker?

#9 Updated by BitingBird about 5 years ago

  • Starter changed from No to Yes

#10 Updated by kytv over 4 years ago

emmapeel wrote:

more user input fresh from today:

double checked in Tails 1.1 :

  • in Seahorse started from Applications → System Tools → Preferences →
    Passwords and Keys it just wourks out of the box, without even the
    workaround :D

It cannot confirm this. Without the workaround the Sync button is greyed out. (Tails 1.3)

  • Seahorse started from Tails OpenPGP Applet → Manage Keys
    it just doesn't work

This is accurate.

#11 Updated by kytv over 4 years ago

intrigeri wrote:

We're patching seahorse.desktop to start it with torsocks. gpgApplet should probably do the same. That's a very simple coding task, any taker?

If just running seahorse with torsocks from gpgApplet would be enough, I can do did it. There will be automated tests for it forthcoming as well.

Not that any of this will take care of this ticket.

#12 Updated by kytv over 4 years ago

I don't think that this is really a regression at all. If it is one it's a really old one.

I found a copy of Tails 0.7.2 and it also has a greyed-out sync button.

#13 Updated by sycamoreone about 3 years ago

Some update for 2.5:

kytv wrote:

If just running seahorse with torsocks from gpgApplet would be enough, I can do did it. There will be automated tests for it forthcoming as well.

Seahorse started from OpenPGP applet now behaves exactly as Seahorse started from the Applications menu: The Sync key is grayed out without the workaround and works with the workaround.

#14 Updated by u about 2 years ago

  • Subject changed from Impossible to synchronize GPG keys using Seahorse to Seahorse does not have a default keyserver selected

Initial title: Impossible to synchronize GPG keys using Seahorse

In Tails 3.0 there is no default keyserver selected, thus, when choosing "Remote" → "Sync and Publish Keys", one cannot sync and has to select a keyserver first.

Next steps:

  • As asked by intrigeri before: "what would be the downside of making this configuration the default? Would Seahorse automatically publish all known public keys to this keyserver (which we don't want)?"
  • If keys are not automatically published, should we make the existing keyserver (hiddenservice) the default?

#15 Updated by u about 2 years ago

  • Subject changed from Seahorse does not have a default keyserver selected to Seahorse does have a configured default keyserver but it's not selected by default
  • Starter deleted (Yes)

Also available in: Atom PDF