Bug #17183
Seahorse fails to import PGP public key
100%
Description
several users reported that since the upgrade to tails 4, they are not able to import PGP public keys anymore from seahorse.
Upstream bug reports:
- https://gitlab.gnome.org/GNOME/seahorse/issues/236
- https://bugs.debian.org/931558
- https://bugs.debian.org/942373
but nobody seems to work on it there.
importing the key from a terminal with gpg --import
should work
Files
Subtasks
Related issues
Related to Tails - Feature #16531: Define our core code base | In Progress | 2019-03-05 | |
Related to Tails - Bug #6568: Mention Seahorse in documentation | Confirmed | 2014-01-05 | |
Blocks Tails - Feature #17247: Core work 2020Q1 → 2020Q2: Technical writing | Confirmed |
History
#1 Updated by goupille 2019-10-24 12:12:57
Bug report: 7a12aedbdd918176d7ccb1a3d5b044c6
Bug report: 3f29c3821f92b1e4b3c0b1254bcad83
Bug report: c411a6718a435e7c42ab17b31071dfb0
#2 Updated by goupille 2019-10-26 11:29:33
Bug report: fac29e2f193a2e2ed2365587931376f3
#3 Updated by intrigeri 2019-10-31 11:42:46
- related to Feature #16531: Define our core code base added
#4 Updated by intrigeri 2019-10-31 11:43:31
- Assignee deleted (
intrigeri)
#5 Updated by intrigeri 2019-10-31 11:43:56
Ouch!
I see that many users are affected.
I’d like us to decide on Feature #16531 what OpenPGP use cases we want (and realistically can) support.
#6 Updated by numbat 2019-11-07 11:29:00
A user has reported that modifying key details has issues as well, I’m not sure if this is related to this issue. Let me know if I should open a new ticket.
#7 Updated by intrigeri 2019-11-10 15:40:11
Hi @numbat,
> A user has reported that modifying key details has issues as well, I’m not sure if this is related to this issue. Let me know if I should open a new ticket.
This seems to be a different problem. At this point we don’t know if they share a single root cause, so yeah, let’s track them separately.
#8 Updated by numbat 2019-11-11 10:19:23
Hello @intrigeri, thanks. I opened a new ticket Bug #17223
#9 Updated by numbat 2019-11-12 10:41:29
A user claims that they were able to import their private PGP key. It doesn’t show up in the list but it is there and can be used.
Bug report: f2d8be746dd1784778124581e4639104
#10 Updated by goupille 2020-01-14 16:51:03
- Assignee set to sajolida
@sajolida, a lot of users are reporting this problem, nobody seems to work on that there, so it may be a good idea to add it to the known issues list, with a more thoroughly workaround documentation for people unfamiliar with command line ?
#11 Updated by emmapeel 2020-01-20 10:33:38
goupille wrote:
> @sajolida, a lot of users are reporting this problem, nobody seems to work on that there, so it may be a good idea to add it to the known issues list, with a more thoroughly workaround documentation for people unfamiliar with command line ?
yes please. also https://www.reddit.com/r/tails/comments/ep13c4/_/feo518d/
Our template goes like:
I think that you are affected by this bug :
https://gitlab.gnome.org/GNOME/seahorse/issues/236
We have this ticket on our own bugtracker to see what we can do on our side :
https://redmine.tails.boum.org/code/issues/17183
In the mean time you should be able to import you keys from a terminal :
Applications>Favorites>Terminal
type the following command (with a space at the end and without pressing 'enter') :
gpg --import
Drag and drop the key file in the terminal and press enter.
#12 Updated by emmapeel 2020-02-12 10:38:24
- Priority changed from Normal to Elevated
i raise the priority for this ticket because many users are facing trouble and contacting us in support.
maybe we can add something to the release notes and/or the https://tails.boum.org/support/known_issues/ page?
#13 Updated by intrigeri 2020-02-21 08:52:12
FWIW I’ve reproduced this problem on my sid system (seahorse 3.34-1).
#15 Updated by sajolida 2020-03-18 17:07:28
- related to Bug #6568: Mention Seahorse in documentation added
#16 Updated by sajolida 2020-03-18 18:06:28
- blocks Feature #17247: Core work 2020Q1 → 2020Q2: Technical writing added
#17 Updated by sajolida 2020-03-18 18:08:30
- Assignee changed from sajolida to cbrownstein
- Target version set to Tails_4.5
- Feature Branch set to doc/17183-import-gpg-key
It’s been a top issue since 4.0 so I consider it as core work (Feature #17247).
Here is a branch; written under the influence of a powerful virus possessing my body, so probably highly buggy!
@cbrownstein: Please have a look!
emmapeel,
goupille, @numbat: Someone from help desk too please :)
#18 Updated by sajolida 2020-03-24 22:21:59
- Status changed from Confirmed to In Progress
#19 Updated by sajolida 2020-03-26 17:58:57
Here is the patch.
#21 Updated by sajolida 2020-04-07 01:33:33
- Status changed from In Progress to Needs Validation
#22 Updated by CyrilBrulebois 2020-04-07 17:05:18
- Target version changed from Tails_4.5 to Tails_4.6
#23 Updated by cbrownstein 2020-04-10 22:37:21
- Assignee changed from cbrownstein to sajolida
I pushed a single small improvement to my branch. Otherwise, looks good!
https://0xacab.org/cbrownstein/tails/-/commits/doc/17183-import-gpg-key
#24 Updated by sajolida 2020-04-14 00:29:58
- Status changed from Needs Validation to Resolved
- % Done changed from 0 to 100
Applied in changeset commit:tails|ced5386cd081ec6feb2ad3ff6d757a5d29ecd09f.
#25 Updated by sajolida 2020-04-14 00:35:14
- Assignee deleted (
sajolida)
emmapeel
goupille @numbat Merged, see: https://tails.boum.org/doc/encryption_and_privacy/gpgapplet#import
#26 Updated by sajolida 2020-04-14 00:36:36
@cbrownstein: Thanks!
emmapeel
goupille @numbat: Merged, see https://tails.boum.org/doc/encryption_and_privacy/gpgapplet#import
#27 Updated by sajolida 2020-05-06 18:00:40
- Status changed from Resolved to Confirmed
- Priority changed from Elevated to Low
- Target version deleted (
Tails_4.6) - Feature Branch deleted (
doc/17183-import-gpg-key)
Documenting is not fixing.