[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#355807: marked as done (Kleopatra can't open .p12 from Thunderbird or Firefox)

Your message dated Tue, 27 Mar 2007 11:05:51 -0400
with message-id <9f694b820703270805v56130f78y4e1cc9ed7b21618d@mail.gmail.com>
and subject line Old bug, do you still have the problem ?
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: Kleopatra
Version: 4:3.4.3-1

Kleopatra can't open a .p12 exported (backup) from Thunderbird or
Firefox (perhaps because they're encrypted backup's?).  Konqueror can
import the encrypted backup's; but when I export those same keys out of
konqueror, kleopatra still can't open them.  This makes Kleopatra
completely & totally unusable for anyone who made a CSR with Firefox at
a CA. I'm using keys from a CA, not self-signed keys.  I made them in
Firefox at the CA's website, as most users of commercial or open CA
certificates would.

This issue is fully reproducible & there are discussions about this
problem elsewhere on the web dating back several months.  Just backup
(the only way to export) your certificates out of Firefox or
Thunderbird, then use KDE crypto to import the backup you just made.
When asked if you want to use the certificate in kmail, answer yes--you
will get the error message.

I am using SimplyMEPIS 3.4-3 to install Debian GNU/Linux (etch/sid)
2.6.15-1-586tsc kernel KDE 3.4 kleopatra 4:3.4.3-1


Lance W. Haverkamp
Contact & encryption info:
 ><> ><> ><>

--- End Message ---
--- Begin Message ---
Submitter was asked to provide more information about this bug
( http://bugs.debian.org/355807 ) four weeks ago.

Since more info was not provided, we are closing the bug.
Feel free to reopen this bug if you are still experiencing this issue
and you have extra information on how reproduce the issue.


--- End Message ---

Reply to: