On 2/23/21 6:55 PM, David C. Rankin wrote:
On 2/23/21 4:59 PM, Carlos E. R. wrote:
On 23/02/2021 23.10, David C. Rankin wrote:
On 2/23/21 2:56 PM, Carlos E.R. wrote:
On 23/02/2021 21.25, David C. Rankin wrote:
...
=========== Sorry Had To Forward, Can't Reply, No Key ==============
What do you mean, no key? Keyboard? GPG key? you do not need them if you do not sign or encrypt.
Forgot to delete that line, had to disable Enigmail in Tbird to be able to reply-to-list. Without disabling tbird wouldn't send due to no gpg key.
I don't want to try just re-importing all my keys until I understand what happened. This is just NUTS. gpg has lost its mind :)
You can create new user, copy the directory ~/.gnupg over, and chown it to the new user. Don't login graphically, use a terminal, do "su -" (don't forget the dash), and then use gnupg tools to verify things, not thunderbird.
You do not need to import anything this way.
Create new user, copied my ~/.gnupg to new user and chowed all to new user. Attempted to list private keys -- nothing. nothing listed at all. (I remembered the 'su -')
I don't know the insides of gpg in detail. I can use it, create or import secret keys, etc., but I don't know how to verify or confirm what is currently wrong with what I currently have? It looks like it is all there to me. It just stopped working....
The same keyring on other boxes work just fine. What happened here?
Something just scrambled my gpg keys. I just pulled a working copy from an Arch box back to my laptop. Ran gpg and listed the secret keys fine. This means I have lost all 3M+ of all the public keys I had imported, and any changes to the private keys made of the past couple of years. Here are the "Working" and "Non-Working" private key listings: Working -rw------- 1 david david 1158 Jul 15 2018 049685C470C32CDB9CCECDB005B3088216E6D0E8.key -rw------- 1 david david 1158 Feb 23 2017 9465CEB4D9BC2DD20856045118D2CCEB9CD68D1D.key -rw-r----- 1 david david 1157 Oct 28 2016 4BCBB4EC81E9771758D140CCE69B7950BD9E5E44.key -rw------- 1 david david 1997 Oct 28 2016 66416C5701166D9EC8C8C011E6C016077C891500.key -rw------- 1 david david 1999 Oct 28 2016 66CB191C42978CC70B81BCC0648C75C5006148C0.key -rw------- 1 david david 1118 Oct 28 2016 78195CD4476C2C7D9EC7EB7C59206781459802DC.key -rw------- 1 david david 1174 Feb 29 2017 00D7206D0D7424C815465B2D62D0829C86052C77.key -rw------- 1 david david 1174 Jul 15 2018 C8BC2254BC819251C5259C708CC0540290969259.key -rw------- 1 david david 682 Nov 4 2016 D27002D1E0701B949B74E1B56B602CCD694E2C91.key -rw------- 1 david david 1921 Oct 28 2016 E51C9622787191B58861C0DDCDBC59119641B074.key -rw------- 1 david david 1116 Oct 28 2016 E60BCC95004E9049DB70E57D2B96CDB409D9D415.key -rw------- 1 david david 814 Oct 28 2016 E7191C4B0ED169E1C981196BC09907DB15DE1719.key -rw------- 1 david david 796 Dec 17 2016 E96DEB07C91B900175909DD665B8B819C49C189D.key Non-working -rw------- 1 david david 1158 Nov 9 2019 049685C470C92CDB9CCECDB005B9088216E6D0E8.key -rw------- 1 david david 1158 Feb 29 2017 9465CEB4D9BC2DD20856045118D2CCEB9CD68D1D.key -rw-r----- 1 david david 1157 Oct 28 2016 4BCBB4EC81E9771758D140CCE69B7950BD9E5E44.key -rw------- 1 david david 796 Oct 90 15:95 66416C5701166D9EC8C8C011E6C016077C891500.key -rw------- 1 david david 1999 Oct 28 2016 66CB191C42978CC70B81BCC0648C75C5006148C0.key -rw------- 1 david david 1118 Oct 28 2016 78195CD4476C2C7D9EC7EB7C59206781459802DC.key -rw------- 1 david david 1174 Feb 29 2017 00D7206D0D7424C815465B2D62D0829C86052C77.key -rw------- 1 david david 1174 Nov 9 2019 C8BC2254BC819251C5259C708CC0540290969259.key -rw------- 1 david david 682 Nov 4 2016 D27002D1E0701B949B74E1B56B602CCD694E2C91.key -rw------- 1 david david 1921 Oct 28 2016 E51C9622787191B58861C0DDCDBC59119641B074.key -rw------- 1 david david 1116 Oct 28 2016 E60BCC95004E9049DB70E57D2B96CDB409D9D415.key -rw------- 1 david david 814 Oct 28 2016 E7191C4B0ED169E1C981196BC09907DB15DE1719.key (key ids have been changed to protect the innocent...) The only event that I can even remotely think of that could have happened, is when I shutdown as the power went out, my office server had already shut down. So when I closed Tbird, shutting down Leap 15, it didn't really shut down and was forced-closed. I know that occurred, because when I logged in yesterday, Tbird launched automatically as I have "Restore previous session" selected in kcontrol Session Manager. So KDE didn't see Tbird as shut down when I shut down my laptop due to the power outage... Now, I have NEVER, in 20+ years, heard of a shutdown like this causing any problems with gpg keys, so this is my best GUESS at what the possible cause is. I hope we have a gpg guru on the list that has thoughts at how to examine the state of the non-working ~/.gnupg files to try and identify what happened. (I have saved both an archive and the actual directory saved under a different name for that analysis) ... at least this is a new and different Linux issue to digest :) -- David C. Rankin, J.D.,P.E.