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

2017-02-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=358392 k...@douglasmcmillan.com changed: What|Removed |Added CC||k...@douglasmcmillan.com --- Comment

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

2016-06-27 Thread Andre Heinecke via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392 --- Comment #16 from Andre Heinecke --- This will be fixed in Gpg4win-3.0.0 / The next beta we will release there. (Probably sometime in the next two weeks) Betas are announced on gpg4win-devel mailing list and can be found under https://wiki.gnupg.org

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

2016-06-27 Thread Andre Heinecke via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392 Andre Heinecke changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|http://commits.kde.or

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

2016-04-29 Thread Andre Heinecke via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392 --- Comment #14 from Andre Heinecke --- I've analyzed this a bit more. Kleopatra is not to blame here I think. As soon as it asks GnuPG "Hey I wish to modify this certificate" GnuPG sends an error "Certificate Expired". I can reproduce it on the command

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

2016-04-08 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392 --- Comment #13 from rigel3925-w...@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 an

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

2016-04-08 Thread Andre Heinecke via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392 Andre Heinecke changed: What|Removed |Added CC||matt...@yahoo.com --- Comment #12 from Andre H

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

2016-04-08 Thread Andre Heinecke via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392 Andre Heinecke changed: What|Removed |Added CC||franzschro...@yahoo.de --- Comment #11 from An

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

2016-03-04 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392 --- Comment #10 from rigel3925-w...@yahoo.com --- There seems to be a subkey in the key I created for myself; however, the "good through date" is the same as the main key. They are both good forever with no expiration date. I couldn't decide when to ex

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

2016-02-22 Thread Andre Heinecke via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392 --- Comment #9 from Andre Heinecke --- The problem is likely that while the primary key is not expired it contains an expired subkey and Kleopatra does not handle this correctly. -- You are receiving this mail because: You are watching all bug changes

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

2016-02-22 Thread Andre Heinecke via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392 Andre Heinecke changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED

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

2016-02-20 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392 --- Comment #7 from rigel3925-w...@yahoo.com --- You're sure there are no incorrect parameters passed to the gpg subsystem? I'm done with this too, because I don't know anything about the interface between gpg and kleopatra. -- You are receiving this

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

2016-02-20 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392 --- Comment #6 from vgv...@yahoo.com --- I have successfully received several encrypted birthday notification emails from Facebook. -- You are receiving this mail because: You are watching all bug changes.

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

2016-02-20 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392 --- Comment #5 from vgv...@yahoo.com --- The certificate that I created for myself to start using Facebook's email encryption says that it is valid "from 2016-01-22 12:55 until forever" in the "Overview" tab of the "Certificate Details" window accessible

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

2016-02-19 Thread Andre Heinecke via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392 Andre Heinecke changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|

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

2016-02-19 Thread Andre Heinecke via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392 Andre Heinecke changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0

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

2016-01-22 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392 --- Comment #2 from vgv...@yahoo.com --- Additionally, I had deleted the gnupg directory containing keyring data and imported my certificate from a backup copy. -- You are receiving this mail because: You are watching all bug changes.

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

2016-01-22 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392 --- Comment #1 from vgv...@yahoo.com --- I have previously relocated my directory "Documents and Settings/" from a solid state drive partition mounted as C: to a normal hard drive partition on another drive letter. The subdirectory "/Application Data/gnu