Bug #9792
Syncing keys in Seahorse does not work in Jessie
100%
Description
Until the test suite scenario is updated this can be verified with the following:
1. `gpg —recv-key —keyserver-options import-clean 0x1D84CCF010CC5BC7`
2. Open Seahorse
3. Enable key synchronization in Edit → Preferences
4. Sync keys from Remote → Sync and Publish Keys
5. Click the Sync button
6. Check the number of signatures with `gpg —list-sigs 0x1D84CCF010CC5BC7`. You should have more than 3 signatures.
This works in Wheezy. It does not in Jessie.
Subtasks
Related issues
|
Blocks Tails - |
Resolved | 2015-07-22 | 2016-01-15 |
History
#1 Updated by intrigeri 2015-08-11 07:15:29
- Assignee set to intrigeri
- Target version changed from Tails_1.8 to Tails_2.0
That’s because our wrapping of seahorse by torsocks, in seahorse.desktop, is apparently not enough: I see direct connections to the keyserver being blocked by the firewall. I tried wrapping seahorse-pgp-keys.desktop the same way, and it is not enough / doesn’t help.
OTOH, running torsocks seahorse in a Terminal gives me a seahorse that can fetch keys perfectly fine.
#2 Updated by intrigeri 2015-08-11 07:15:50
- blocks
Bug #9791: Update torified_gnupg feature for Jessie added
#3 Updated by intrigeri 2015-08-11 07:16:11
- Priority changed from Normal to High
(Blocks a high prio ticket.)
#4 Updated by intrigeri 2015-08-11 07:20:00
- blocks #8668 added
#5 Updated by intrigeri 2015-08-26 06:12:33
- Deliverable for set to 268
#6 Updated by intrigeri 2015-10-03 04:13:32
- Target version changed from Tails_2.0 to Tails_1.8
#7 Updated by intrigeri 2015-11-09 03:25:21
- Status changed from Confirmed to Resolved
- % Done changed from 0 to 100
Applied in changeset commit:7a536e699cc26dc1451a69cf8e477b5a1a48779b.
#8 Updated by intrigeri 2015-11-09 03:26:13
- Assignee deleted (
intrigeri) - Target version changed from Tails_1.8 to Tails_2.0