Bug 336538

Summary:	Konqueror To Accept CA Certificates For Online Banking
Product:	[Unmaintained] kio	Reporter:	Nenad Latinović <nenad>
Component:	kssl	Assignee:	Konqueror Bugs <konqueror-bugs-null>
Status:	CONFIRMED ---
Severity:	normal	CC:	adawit, nenad
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Nenad Latinović 2014-06-21 07:55:03 UTC

Hi.

Basically, i love the browser, but what I would need for it to complete the experience, is for it to allow me to import my CA Digital Certificate (.p12 extension) for online banking. Without it, Konqueror is pretty much useless for me. 

Thankful in advance.

Reproducible: Always

Comment 1 Christoph Feck 2014-06-21 11:40:22 UTC

In System Settings, there should be "SSL Preferences" (or alternatively, run "kcmshell4 kcm_ssl").

Please check if adding your certificate there works.

Comment 2 Nenad Latinović 2014-06-21 19:29:56 UTC

Hi. Thanks for your response.

It doesn't work. It doesn't recognize neither my .p12 nor .pem certificate.

Any further steps i should take?

Comment 3 Dawit Alemayehu 2014-11-07 03:56:19 UTC

(In reply to Nenad Latinović from comment #2)
> Hi. Thanks for your response.
> 
> It doesn't work. It doesn't recognize neither my .p12 nor .pem certificate.
> 
> Any further steps i should take?

It should recoginze the .pem file so long as it is not protected by password. There is no support for .p12 file since KDE now relies on Qt for SSL support now. Unfortunately support for PKCS12 certificate bundles was added to Qt in Qt 5.4:

https://bugreports.qt-project.org/browse/QTBUG-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel

As such the option to import your own personal certificate will not be present in KDE 4.x series. It will probably be restored in KDE frameworks.

Comment 4 Justin Zobel 2021-03-11 01:23:50 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.