Created attachment 1022574 [details] Error message Description of problem: Thunderbird is not able to import certificate. Version-Release number of selected component (if applicable): thunderbird-31.6.0-1.fc21.x86_64 How reproducible: Steps to Reproduce: 1) Issue certificate at a valid CA (e.g., Globalsign). 2) Attempt to import it 3) Insert password 4) Get error message (see attachment): "The PKCS #12 operation failed for unknown reasons." Actual results: Expected results: Certificate gets imported without issues. Additional info: Works flawlessly on Ubuntu 15.04.
Perhaps you could help us there, Kai?
Please check if your .p12 file is okay, for example by: openssl pkcs12 -info -in file.p12 It should output your private key to stdout (and also certificate).
Hi, I got two certificates from them: When I saw that I couldn't import their certificates neither on my office workstation (F21) nor on my notebook (also F21), I came to the conclusion their cert must be defective; instantly I received a new one, which also didn't work (no import on Thunderbird or Firefox). I tried to export, delete and re-import my existing (years old) certificate -- works like a charm Then I tried to import the new one on an Ubuntu 15.04 VM -- worked like a charm. So my conclusion was that F21 has a problem here (verified on two machines). Tried following with both (new) certs, same output, they're okay: [tis@relentless ~]$ openssl pkcs12 -info -in PC201505061774.pfx Enter Import Password: MAC Iteration 2000 MAC verified OK PKCS7 Data Shrouded Keybag: pbeWithSHA1And3-KeyTripleDES-CBC, Iteration 2000 (...) subject=/CN=schoeler.inter.net/emailAddress=schoeler issuer=/C=BE/O=GlobalSign nv-sa/CN=GlobalSign PersonalSign 1 CA - SHA256 - G2 Best regards, Timo
Please download and install following debug build from copr: http://copr.fedoraproject.org/coprs/xhorak/thunderbird-debug/builds/ Then run thunderbird in terminal by: NSPR_LOG_MODULES=pipnss:5 thunderbird Then try to import the cerificate and attach debug output which is created during run.
(In reply to Jan Horak from comment #4) > Please download and install following debug build from copr: > http://copr.fedoraproject.org/coprs/xhorak/thunderbird-debug/builds/ > > Then run thunderbird in terminal by: > NSPR_LOG_MODULES=pipnss:5 thunderbird > Then try to import the cerificate and attach debug output which is created > during run. Hi Jan, thanks for your reply. Log file attached.
Created attachment 1029825 [details] Log file created by thunderbird-debuginfo-31.7.0-1.fc21.x86_64.rpm
Thanks for the log. According to log file you're hitting following error: -1088788672[7faebde1e6e0]: PKCS12: NSS/NSPR error(-8099) -1088788672[7faebde1e6e0]: PKCS12: I called(7) The -8099 is: SEC_ERROR_PKCS12_UNABLE_TO_IMPORT_KEY -8099 Unable to import. Error attempting to import private key. This seems to be problem in NSS code, reassigning to nss component.
Thanks for reassigning. FYI, just updated to Fedora 22 (thunderbird-31.7.0-1.fc22.x86_64), didn't change anything: Error persists.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Hi, I reopened the ticket because the problem still persists with bleeding edge Fedora 23.
Again verified the certificate is okay.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Bug is still not solved (F24).
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Hi, is there any news on that? I can still see that problem. A few minutes ago my coworker (also Fedora 25) ran into the same issue and found this very bug after searching the web for a solution. Best, Timo
I just got myself a free certificate from https://www.startcomca.com/ and it works. GlobalSign PersonalSign 1 CA - SHA256 - G2 does still not work. Seems to be a problem of the CA.
I was told that people can fix by importing their GlobalSign PersonalSign 1 CA - SHA256 - G2 certificate into Microsoft Internet Explorer and then re-exporting it. Then it would work for Thunderbird (on Linux, BSD, ...), too. I asked if they have plans to inform people who have ordered one of these (broken) certificates in the past. I got this answer. "Honestly, we have hardly any customers that are affected by this. The majority who are, were able to import, then export a new pfx from IE and it resolved the issue. The issue isn't the certificate not working, so much as a compatibility issue with certain platforms. The most commonly used though are supported, and as I mentioned, those aren't we've been able to work around. Given the very few customers that have not been able to resolve their issue due to this, I don't expect a mass communication to go out, as it would likely cause more confusion and unnecessary inquiries, then actually be helpful knowledge. If you'd like to me to update you when I find out the exact date of the release, please let me know."