Bug 156954 - Importing certificates into kleopatra should offer to import into Konqueror, too.
Summary: Importing certificates into kleopatra should offer to import into Konqueror, ...
Status: RESOLVED INTENTIONAL
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: Marc Mutz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-30 07:33 UTC by Richard Hartmann
Modified: 2013-05-08 10:08 UTC (History)
2 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 Richard Hartmann 2008-01-30 07:33:47 UTC
Version:            (using KDE 3.5.8)
Installed from:    Debian testing/unstable Packages

When you import a CA certificate into Konqueror, it will ask you if you want to make it available to KMail, i.e. kleopatra.
When you import a CA certificate into kleopatra, no such thing happens.

This is especially annoying as kleopatra is suggested as default handler for PEM files. If a user receives a certificate per email, he needs to save it to a file, go to Konqueror, enter the settings menu and add the certificate by hand.

Filed as bug as it is working the other way around.

Filed against 3.5.8 as KDE PIM is not in 4.0 so I could not test it there.
Comment 1 Marc Mutz 2008-05-27 13:57:15 UTC
Am I right in assuming that you are really reporting this bug against KDE 4.0? If so, kdepim is not part of the KDE 4.0 release, so it's not surprising that there's no kleopatra to handle the import.

Closing for 4.1.0, on the assumption that the above is correct. If it isn't, reopen and provide more details.

Thanks.
Comment 2 Richard Hartmann 2008-05-30 04:38:42 UTC
Well, the bug does exist in 3.5.8, but unless there will be a 3.5.10 or 3.6, it will prolly not get fixes in the 3.x branch. I am reopening as I am in the middle of nowhere atm and fear the report will get lost, otherwise. Could you confirm this works as intended in 4.1? If yes, please reclose and my apologies for causing extra work.

If not, please tell me what kind of details you would like. To me, the report is clear, but then, I do have the advantage of knowing what I mean before even reading my own text, so I am hardly objective.

Thanks,
Richard
Comment 3 Marc Mutz 2008-06-12 16:53:09 UTC
- Do you have kdepim/kleopatra installed?
- does
  kleopatra --import-certificate <filename> works?
- does
  gpgsm --import < <filename> work?
- if not, what's the error?
Comment 4 Richard Hartmann 2008-06-12 17:34:51 UTC
- Do you have kdepim/kleopatra installed? 

Yes.

Importing the certificate by hand works, as well.

The reason why I filed a report is because it does not offer to do so, automagically. I.e. I do not want to have to import the same certificate twice, _especially_ as you will get asked if you want both Kleopatra & Konqueror to use the certificate if you import it into Konqueror.
Comment 5 Marc Mutz 2008-06-17 00:15:46 UTC
Ok, I think now I've got it. Not a bug, though. New feature, but one that's nice to have, I agree. If you want to help, find out how to access the cert store of Konqueror/KSSL/whatever it's called these days, programmatically (like: DBUS, command line args).

Thanks,
Marc
Comment 6 Emanuel Schütze 2013-05-08 10:08:42 UTC
I think, this issue is outdated. Please reopen if you can give us more information for current KDE/Kleopatra version.