[kleopatra] [Bug 358392] Key could not be certified. Certificate expired, but NOT!

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358392

--- Comment #13 from rigel3925-w8v2 at yahoo.com ---
Since my last comment I have stopped using Windows XP (32 bit) due to Google
Chrome announcing an end of support date. I installed Windows 7 64-bit on a
fresh partition along with Thunderbird, Enigmail and Kleopatra. I've redirected
my documents directories to another drive partition, but I have left "documents
and settings" alone since it's protected and I haven't blindly followed
anyone's hacks yet.

I still get the same error when trying to certify Facebook's public certificate
which is the only other certificate besides my own I have stored so far:

The certificate could
not be certified.
Error: Certificate
expired

My certificate is valid forever, and Facebook's is valid until 2018-05-17; two
more years from now.
    .    .    .
I now see under "Technical Details" that Facebook's certificate has a part that
will expire on 2016-06-12, two months from now, and a part that expired
2015-11-14, before I started trying to certify the certificate. 

Facebook has two fingerprints published--one for the main key and one for an
"operational subkey". Instead having only one personal certification for the
entirety of Facebook's certificate, it appears that each component part of the
certificate should be independently certified with the different published
fingerprints. The code in Kleopatra needs to be expanded in this way.

Is encrypted email starting to take off and become ubiquitous now?

-- 
You are receiving this mail because:
You are on the CC list for the bug.