On 9/22/22 03:36, Carlos E. R. wrote:
On 2022-09-21 20:31, Lew Wolfgang wrote:
On 9/17/22 13:31, David C. Rankin wrote:
On 9/17/22 13:24, Carlos E. R. wrote:
Only the software development engineers know for certain what needs to be protected and backed up. The TB update process/software should preserve and backup all user data before proceeding with an irreversible upgrade.
Even if they do, there is no way to revert the process once the admin upgraded the code.
Imagine my F'ing surprise when Mozilla asked me test 102-beta on the CPU use issue, damn glad I backup up my TB directory before that. When I was done, I just wiped the TB directory and restored from the backup and went back to TB 91 -- that works.
The biggest rub is there is NO WARNING. There should at least be a notice and (yes/no) prompt to the user explaining the irrevocable change that is about to occur.
It happened to me two days ago without warning! It scrambled my saved messages to some degree, but worse, it broke Smartcard S/MIME encryption. I can decrypt existing messages, but encrypting new ones fails.
I'm screwed! I'm having to use Outlook!!
Use older Thunderbird.
Me, I just tried mime pkcs, and I can at least sign emails - with the old th I could not.
But I had to go to the configuration, erase the certificate, and add it again.
Funny thing, my certificate doesn't have an email defined (an error), so if I want to send to my email an encrypted email, it does not find the certificate, and it does not allow to choose one. It selects an older one that has an email defined, and when going to send it fails because it says the certificate is expired.
You might want to try a fork of Thunderbird, Betterbird.
https://www.meneame.net/story/betterbird-cliente-correo-open-source-gratuito...
I didn't know there was a Betterbird! But Thunderbird is fine, we've been using it with smartcard/S/Mime for decades. It's just 102 that's broken. Note that it decrypts just fine, the problem has something to do with processing the certs on the card. I create a new message with addresses for which I have public certs. My smartcard is not plugged in. I can hit the "View Security Info" button and it finds all the addressee certs and tells me their expiration date and that they're "Valid". Now, doing nothing else, I plug in my smartcard and hit the View Security Info button again. Now all the certs are marked "Invalid" and I can't send the message. I tried this on two separate systems, so its not just a sample defect on my one box. I can read previously encrypted traffic, I just can't encrypt new traffic. So yup, using an older Thunderbird and zypper locking it is the answer. but only after restoring the local message database from backups. Granted, I didn't try going back without restoring the database, but that's what this thread was about in the first place. Too bad Betterbird isn't in the openSUSE repos. Regards, Lew