Bug 269498

Summary:	Konqueror cannot use certificates to authenticate
Product:	[Unmaintained] kio	Reporter:	Christopher Yeleighton <giecrilj>
Component:	kssl	Assignee:	Konqueror Developers <konq-bugs>
Status:	REPORTED ---
Severity:	normal	CC:	bugs, gleirsch, heri+kde, ro.ggi, s.suther
Priority:	NOR
Version First Reported In:	4.6
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Christopher Yeleighton 2011-03-26 23:04:37 UTC

Version:           4.6 (using KDE 4.6.0) 
OS:                Linux

Start SSL requires certificate-based authentication.  Konqueror is unable to provide the necessary certificate.  Moreover, it cannot be used to generate a new certificate either.

Reproducible: Always

Steps to Reproduce:
  0. Create an account at Start SSL [1] and import the personal certificate issued into Kleopatra.
  1. Tell Konqueror to visit Start SSL control panel [2].

Actual Results:  
  1. Server auth.startssl.com rejected connection.

Expected Results:  
  1. Konqueror should use the certificate available in Kleopatra to authenticate.

OS: Linux (x86_64) release 2.6.37.1-1.2-desktop
Compiler: gcc

___
[1] <URL: https://www.startssl.com/ >
[2] <URL: https://auth.startssl.com/ >

Comment 1 gleirsch 2011-04-19 12:12:48 UTC

Can confirm this issue for KDE/Konqueror 4.5.1 in Kubuntu 10.10.

Although I'd rather like to use rekonq, I had to switch over to konqueror because rekonq still not seems to use the kleopatra certificate service/store/part.
Maybe even for Konqueror this is not a technical issue but a feature request. I read that in earlier versions of KDE there were Crypto settings in KDE control centre and konqueror?

Comment 2 Samuel Suther 2013-10-24 10:48:22 UTC

Confirm the Error:

rekonq 0.9.1 on KDE 4.8.5

Ubuntu 12.04

Comment 3 Dawit Alemayehu 2013-12-29 16:18:03 UTC

*** Bug 244806 has been marked as a duplicate of this bug. ***

Comment 4 Dennis Schridde 2015-02-03 08:22:20 UTC

Duplicate of #162485 (via bug #205968), or duplicate of bug #178806.

Comment 5 Justin Zobel 2021-03-10 00:15:32 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.