Bug 315816 - Won't import certificate issued by Symantec.
Summary: Won't import certificate issued by Symantec.
Status: RESOLVED DUPLICATE of bug 333310
Alias: None
Product: kleopatra
Classification: Applications
Component: Assuan UI Server (show other bugs)
Version: 2.1.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Andre Heinecke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-26 16:18 UTC by ashtongj
Modified: 2016-04-08 16:54 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ashtongj 2013-02-26 16:18:04 UTC
I obtained an email X.509 certificate from Symantec, and exported it using the Windows Internet Options dialog, with the secret key. When I tried to import it a warning box was displayed with the title "Certificate Import Failed - Kleopatra" and the text "Could not determine certificate type of [file name]".

Reproducible: Always

Steps to Reproduce:
1. Obtain Symantec email certificate (the one that costs around US$25).
2. Import to Windows 7.
3. In Control Panel, select Internet Options
4. Select Content tab
5. Click Certificates
6, Select the certificate of interest and click Export.
7. Next.
8. Choose "Yes, export the private key".
9. The only format offered for the export will be Personal Information Exchange. Click the "Include all certificates in the certification path" option and leave the other two options unselected. Click next.
8. Choose a password, Next.
9. Choose a file name, and complete the dialog in the obvious manner.
10. In Kleopatra, click the "Import Certificates" button in the upper left of the Window.
11. In the Select Certificate File dialog, navigate to the file created in step 9.
12. Click Open, and warning box appears.

Actual Results:  
Warning box appeared.

Expected Results:  
Imported certificate.
Comment 1 Emanuel Schütze 2013-05-10 06:27:59 UTC
Which certificate file format do you try to import in Kleopatra?
Comment 2 ashtongj 2013-05-17 14:24:00 UTC
The file extension in Windows 7 is .pfx

The warning box is titled "Certificate Import Failed - Kleopatra"

The warning box has a red rectangle with a white cross on the left side, and the words
"Could not determine certificate type of
C:/Users/Gerard/Documents/Crypto/Certificates/SymantecJan2013fromWindowsInternetOptions.pfx"
Comment 3 Anupam 2013-06-21 12:36:33 UTC
Have the same issue with a Comodo issued Cert. This problem looks to be CA agnostic.

Any workarounds?
Comment 4 Emanuel Schütze 2013-06-24 15:06:00 UTC
Confirmed this import error with Kleopatra 2.1.1 from Gpg4win 2.1.1:
Import *.pfx certificate file
-> "Could not determine certificate type of ..."

Note: Imort of same .pfx file works with Kleopatra 0.40!

@aheinecke: can you look at this issue please?
Comment 5 ashtongj 2013-12-04 19:28:22 UTC
I have found a workaround. I imported the key into Firefox, then exported it as a .p12 file. I was able to import the .p12 file, and verify that it worked by encrypting and decrypting a file.
Comment 6 ashtongj 2013-12-11 16:04:38 UTC
I spoke too soon about finding a workaround. Although I can import the .p12 file exported from Firefox, I cannot encrypt a file with it. When I try, the message in the results window indicates "Encryption failed" and "No value".
Comment 7 siebel 2014-03-05 15:55:14 UTC
Has anybody find a solution for the described problem in the meantime? I have the same problem with GnuPG. The file encryption via PGP is possible without any problem. The encryption via X509/SMIME ends in the failure: "encryption failed" "no value". 

The software GnuPG and Kleopatra runs under Win XP. The certificate has been issued by S-TRUST (www.s-trust.de). 

I hope very much, that a solution for this is possible. 

Is there any alternative software on market?

Greetings, Maik
Comment 8 Andre Heinecke 2016-04-08 16:54:34 UTC
I've fixed pfx import.

*** This bug has been marked as a duplicate of bug 333310 ***