On 11/11/20 3:08 AM, Carlos E. R. wrote:
On 11/11/2020 10.04, David C. Rankin wrote:
On 11/10/20 1:03 PM, Carlos E. R. wrote:
Now I try to send a message, and this time it does find my key, as my public key is imported. But the email is not really signed.
I repeat the try, making sure I click on sign - this time it is indeed signed.
It does not recognize my email in this thread as signed. This morning it did, but could not import the key. No PGP context or local menu. Alpine uses inline PGP. Th appears to recognize my just sent test email in the sent folder as signed (but flags as "uncertain"). I mark the key as trusty, and now it displays a little green check mark.
What a mess.
TB 68.12 -- and happy, see no reason to experiment with my production mailer.
Too late for me. I forgot to lock the package. And on laptop1 I already updated to Leap 15.2, so also too late.
Phew! I'm running 15.2 here and forgot to lock t-bird 68 too, but so far it looks like it's working for me and my users. Comments: First, I'd like to thank Thunderbird's devs and maintainers for making Thunderbird possible. It's one of those critical Linux applications that make it possible for us to use Linux in our production desktop environment. Without it and its support for PKI Smartcards we'd be using Windows 10 on desktops, and openSUSE on the back-end servers. Second, I'm happy to report that message signing and encryption works with Smartcards! This is The Key capability in Thunderbird for us. We're using the standard pcscd driver and opensc packages for the middleware. libcoolkey is falling behind and doesn't support PIV Smartcards. Third, the look and feel is certainly different, but I'm sure we can adapt. Forth, I believe that running 78 updates your .thunderbird profile to the point where you can't go back to 68. I've seen this happen with the Windows version of Thunderbird, so it might be prudent to make a backup of ~/.thunderbird before running 78 for the first time just in case. Regards, Lew