Bug #7051
Seahorse does have a configured default keyserver but it's not selected by default
0%
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.
Files
Subtasks
Related issues
|
Related to Tails - |
Resolved | 2013-10-31 |
History
#1 Updated by intrigeri 2014-04-10 06:02:39
- Priority changed from Normal to Elevated
Bumping priority, assuming that’s a regression.
#2 Updated by sajolida 2014-04-12 10:45:55
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 2014-04-12 12:24:35
- 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 2014-04-17 08:30:46
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 2014-05-29 07:59:25
- related to
Bug #6394: Seahorse launched from the gpgApplet cannot search for public keys added
#6 Updated by sajolida 2014-08-01 15:15:33
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 2014-08-16 08:06:26
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 2014-08-16 08:34:43
> * 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 2014-08-17 17:18:51
- Starter changed from No to Yes
#10 Updated by kytv 2015-02-24 22:52:27
emmapeel wrote:
> more user input fresh from today:
>
> h3. 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 2015-02-25 02:41:26
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 2015-02-25 18:07:19
- File tails-0.7.2-seahorse.png added
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 2016-08-19 08:26:49
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 Anonymous 2017-06-30 13:02:33
- 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 Anonymous 2017-06-30 13:02:59
- 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)