Version: (using Devel) Installed from: Compiled sources I'm tried to import the p12 certificate with this console result: registerCommand( 0xd15390 ) KeyListController::Private::slotActionTriggered: not implemented KeyListController::Private::slotCommandFinished( 0xd15390 ) KeyListController::Private::slotDestroyed( 0xd15390 ) GUI displays the dialogue attached bellow.
Created attachment 26798 [details] screenshot This issue is may be tied with this Bug 168559
environment Qt: 4.4.0 KDE: 4.1.1 (KDE 4.1.0 (4.1 >= 20080722)) "release 26.3" Kleopatra: 2.0.0-rc1 openSUSE 11 64-bit
This looks like you mistyped the passphrase. Did pinentry come up? Does it work on the command line, like this: gpgsm --import < foo.p12 ?
I haven't got experience with certificates on the Linux platform yet. Sorry :?) I tried this command with the results below. sample openVPN certificate: nesnera@nesnera-nb:~> gpgsm --import < /usr/share/doc/packages/openvpn/sample-keys/pkcs12.p12 gpgsm: gpgsm: GPG_TTY has not been set - using maybe bogus default gpgsm: gpg-protect-tool: 1760 bytes of RC2 encrypted text gpgsm: gpg-protect-tool: processing certBag gpgsm: gpg-protect-tool: processing certBag gpgsm: gpg-protect-tool: 640 bytes of 3DES encrypted text gpgsm: gpg-protect-tool: keygrip: 47B90E4C052C6694CA6AD10B520655C19163D9C5 gpgsm: gpg-protect-tool: secret key file `/home/nesnera/.gnupg/private-keys-v1.d/47B90E4C052C6694CA6AD10B520655C19163D9C5.key' already exists gpgsm: certificate is good gpgsm: total number processed: 3 gpgsm: unchanged: 2 gpgsm: secret keys read: 1 gpgsm: secret keys unchanged: 1 secmem usage: 0/16384 bytes in 0 blocks my Thawte's test certificate: nesnera@nesnera-nb:~> gpgsm --import < /home/nesnera/documents/ThawteNesneraTestovaci.p12 gpgsm: gpgsm: GPG_TTY has not been set - using maybe bogus default gpgsm: gpg-protect-tool: 1224 bytes of 3DES encrypted text gpgsm: gpg-protect-tool: decryption failed; trying charset `ISO-8859-1' gpgsm: gpg-protect-tool: decryption failed; trying charset `ISO-8859-15' gpgsm: gpg-protect-tool: decryption failed; trying charset `ISO-8859-2' gpgsm: gpg-protect-tool: decryption failed; trying charset `ISO-8859-3' gpgsm: gpg-protect-tool: decryption failed; trying charset `ISO-8859-4' gpgsm: gpg-protect-tool: decryption failed; trying charset `ISO-8859-5' gpgsm: gpg-protect-tool: decryption failed; trying charset `ISO-8859-6' gpgsm: gpg-protect-tool: decryption failed; trying charset `ISO-8859-7' gpgsm: gpg-protect-tool: decryption failed; trying charset `ISO-8859-8' gpgsm: gpg-protect-tool: decryption failed; trying charset `ISO-8859-9' gpgsm: gpg-protect-tool: decryption failed; trying charset `KOI8-R' gpgsm: gpg-protect-tool: decryption failed; trying charset `IBM437' gpgsm: gpg-protect-tool: decryption failed; trying charset `IBM850' gpgsm: gpg-protect-tool: decryption failed; trying charset `EUC-JP' gpgsm: gpg-protect-tool: decryption failed; trying charset `BIG5' gpgsm: gpg-protect-tool: data error at "decrypted-text", offset 4292581553 gpgsm: gpg-protect-tool: error at "bag-sequence", offset 15 gpgsm: gpg-protect-tool: error parsing or decrypting the PKCS-12 file gpgsm: error running `/usr/lib64/gpg-protect-tool': exit status 2 gpgsm: total number processed: 0 secmem usage: 0/16384 bytes in 0 blocks
This looks like a problem with the certificate, or gpgsm not being able to deal with the certificate. Please report this against gpgsm at http://bugs.gnupg.org. You may link to this bug report here, though I'm closing it as invalid here.