Seahorse 43.0 on MX 23 not importing public keys  [Solved]

Message
Author
linuxbeliever
Posts: 18
Joined: Wed Apr 03, 2019 1:28 am

Seahorse 43.0 on MX 23 not importing public keys

#1 Post by linuxbeliever »

Hi! Everyone.

I having a hard time importing public keys on seahorse 43.0 on MX 23. When I try to import, it displays the warning that the key is not signed, but you still click on the import button at upper right corner of the window, when I click the window goes away, but the key does not show up in the list of keys on the GNUPG keys section/list. I done some research and I read that this seahorse 43.0 version has a bug in it. Somebody said that the workaround is to do the import by CLI (COMMAND LINE), by executing this command, and then seahorse will display the public key you are importing.

Code: Select all

maverick2@TopGun2:~
$ cd ~/Downloads/Android\ Openkeychain/
maverick2@TopGun2:~/Downloads/Android Openkeychain
$ ls
'Android Openkeychain keys backup code'                                                                                'issue importing BLU C5L cellphone on linux mint 21.2  Openkeychain 5.8.2 (58902)_2023-10-20_14-36-22.png'
 backup_2023-10-20.pub.pgp                                                                                             'MX-23.1_ahs_x64 Libretto July 31  2023 base: Debian GNU-Linux 12.txt'
 backup_2023-10-20.sec.pgp                                                                                             'Official web site for gnome seahorse 2023-10-20_19-41-28.png'
'Error importing BLU C5L cellphone with Openkeychain 5.8.2 (58902) on MX 23 on seahorse 43.0 2023-10-20_14-36-22.txt'  'Seahorse 43.0 runing on MX-23.1_ahs_x64 Libretto July 31  2023 base: Debian GNU-Linux 12_2023-10-20_18-47-09.png'
'forum.mxlinux.org-GnuPGP - MX Linux Forum.pdf'                                                                        'seahorse on Linux Mint 21.2 Victoria base_ Ubuntu 22.04 jammy_2023-10-20_14-10-03.png'
maverick2@TopGun2:~/Downloads/Android Openkeychain
$ sudo gpg --import backup_2023-10-20.pub.pgp
[sudo] password for maverick2:          
gpg: /root/.gnupg/trustdb.gpg: trustdb created
gpg: key AB0A0AE8468D0402: public key "Pablo Reyes <pabloreyes1021@gmail.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1
maverick2@TopGun2:~/Downloads/Android Openkeychain
$
But, when I run seahorse 43.0, the public key is not displayed in the list of GNUPG keys, see below for proof. :confused:
seahorse 43 running on MX 23 2023-10-21_15-01-21.png
The official web site for seahorse, says that as of today which is 10/21/23 the stable version is seahorse 40.
Official web site for gnome seahorse 2023-10-20_19-41-28.png
Just so you know, I have a another system running linux mint 21.2 with seahorse 41, and the importing worked. :number1:
seahorse 41 running on linux mint 21.1 2023-10-21_14-49-57.png
The only idea I have is try to compile the one on the official web site, what do you think? 9_9 Any ideas? Thanks for your time and help.
You do not have the required permissions to view the files attached to this post.

User avatar
fehlix
Developer
Posts: 12886
Joined: Wed Apr 11, 2018 5:09 pm

Re: Seahorse 43.0 on MX 23 not importing public keys  [Solved]

#2 Post by fehlix »

linuxbeliever wrote: Sat Oct 21, 2023 6:14 pm

Code: Select all

$ sudo gpg --import backup_2023-10-20.pub.pgp
[sudo] password for maverick2:          
gpg: /root/.gnupg/trustdb.gpg: trustdb created
gpg: key AB0A0AE8468D0402: public key "Pablo Reyes <pabloreyes1021@gmail.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1
$
But, when I run seahorse 43.0, the public key is not displayed in the list of GNUPG keys, see below for proof.
Seahorse v. 43.0 (aka "Password & Keys") works here.
You may want after import switch from the default view "personal" (you'r private keys):
seahorse-show-pesonal.png
to view "trusted" or to view "any" key:
seahorse-show-any.png
Also, you may not want import on CLI with "sudo gpg --import" b/c that would not not be your keyring but rather root's keyring.
And Seahorse will only show keys from users keyring.
Note further: In my example I have only imported my public key, not my private key, so it looks similar to what you have tried to achieve.
You do not have the required permissions to view the files attached to this post.

linuxbeliever
Posts: 18
Joined: Wed Apr 03, 2019 1:28 am

Re: Seahorse 43.0 on MX 23 not importing public keys

#3 Post by linuxbeliever »

Hi! fehlix

Okay! Your suggestion worked! Thanks a million!!!!. It only took me 3 clicks outside the GNUpg keys category to refresh the list, it is kind of slow to refresh the list by itself. I now only need to change the key I imported to the root's keyring, to a normal user like you said. Do you know a way to do that, is it possible to do it on seahorse as a normal user or do I have to do it by CLI command and what is the syntax/spelling of that command? Would you please show me? Thanks for your time and help.

User avatar
fehlix
Developer
Posts: 12886
Joined: Wed Apr 11, 2018 5:09 pm

Re: Seahorse 43.0 on MX 23 not importing public keys

#4 Post by fehlix »

linuxbeliever wrote: Sun Oct 22, 2023 2:20 pm Hi! fehlix

Okay! Your suggestion worked! Thanks a million!!!!. It only took me 3 clicks outside the GNUpg keys category to refresh the list, it is kind of slow to refresh the list by itself. I now only need to change the key I imported to the root's keyring, to a normal user like you said. Do you know a way to do that, is it possible to do it on seahorse as a normal user or do I have to do it by CLI command and what is the syntax/spelling of that command? Would you please show me? Thanks for your time and help.
You would just import the keys with Seahorse (aka "Passwords & Keys"). Not sure why you want to do this from the command line. Maybe you give some more explanation why you think you can't import pub-keys with Seahorse.

linuxbeliever
Posts: 18
Joined: Wed Apr 03, 2019 1:28 am

Re: Seahorse 43.0 on MX 23 not importing public keys

#5 Post by linuxbeliever »

You would just import the keys with Seahorse (aka "Passwords & Keys"). Not sure why you want to do this from the command line. Maybe you give some more explanation why you think you can't import pub-keys with Seahorse.
I meant to say, if the publishing as root was reversible, so the creation of the key in root is modifying crusial settings in root ( 'root' ), I do not like to have things that they are not supposed to be in restricted locations, I remember the command said it created the 'root' location, can that creation be undo/reversed? Thanks for your time and help.

Post Reply

Return to “Software / Configuration”