I´d very much like your opinion on a certain matter.
I had reason to use seahorse (GNOME front end for GnuPG). The reason itself is a different matter which I will talk about in a different thread (Revoking signature of GnuPG-key in seahorse ).
I should have know better - and although I really did - I stupidly used the command “sudo seahorse” which opened up the GUI alright.
I didn´t perform any action at all but was a bit concerned about unintentionally having changed permissions by using “sudo” instead of
“gksudo” (which is recommended for GUI applications).
On https://askubuntu.com/questions/523571/why-am-i-unable-to-access-openpgp-keys-on-seahorse-and-access-encrypted-files I found a similar topic being dealt with:
The problem is that you ran GnuPG as root at some time, and it created your keyring files with root being the owner […]
Run sudo chown -r bill:bill /home/bill/.gnupg (user folder guessed from user name) to repair the file ownership.
I didn´t run any GnuPG-related commands per se as root, just seahorse. Nevertheless I looked up my .gnupg-folder:
ll /home/rosika/.gnupg insgesamt 712K drwx------ 2 rosika rosika 4,0K Mär 22 2019 crls.d/ -rw-r--r-- 1 rosika rosika 276 Mär 22 2019 gpg-agent.conf drwx------ 2 rosika rosika 4,0K Mär 22 2019 openpgp-revocs.d/ drwx------ 2 rosika rosika 4,0K Mär 22 2019 private-keys-v1.d/ -rw-rw-r-- 1 rosika rosika 315K Feb 21 13:28 pubring.kbx -rw-rw-r-- 1 rosika rosika 313K Feb 20 16:43 pubring.kbx~ -rw------- 1 rosika rosika 600 Feb 21 15:07 random_seed -rw-r--r-- 1 rosika rosika 48K Feb 21 13:28 tofu.db -rw------- 1 rosika rosika 1,5K Feb 21 14:29 trustdb.gpg
It seems the permissions are alright after all.
So what do you think: is there anything I should do or can I leave it at that?
Thanks for your help.