By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 594 - konqueror does not save site certificates
Summary: konqueror does not save site certificates
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdelibs (show other bugs)
Version: 3.5.13 [Trinity]
Hardware: i386 Debian Squeeze
: P5 critical
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2011-11-08 16:55 CST by Nikolaus Klepp
Modified: 2012-10-19 15:45 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String: TDE 3.5.13
Application Version:
Application Name: konqueror

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nikolaus Klepp 2011-11-08 16:55:14 CST 
Go to a https-site with unknown certificate, e.g. https://www.ba-ca.at

A messagebox appears saying "The IP address of the host www.ba-ca.at does not match the one the certificate was issued to." That's what it is supposed to do. The problem is, that konqueror does not store the certificate so that I do not get that messagebox again.

When you click "Continue" on the messagebox, then the next messagebox appears 
saying:

"Would you like to accept this certificate forever without being prompted?"

Click "Forever" and close konqueror. At this point the site certificate should 
have been saved to ~/.trinity/share/config/ksslpolicies - but it is not.

Now restart konqueror, go to the same address as before and you get the 
messagebox "The IP address of the host www.ba-ca.at does not match the one 
the certificate was issued to." - which should not appear as the site 
certificate should have been stored in ~/.trinity/share/config/ksslpolicies. 

This problem is quite anoying, as it appears on all self certified sites and 
sites.
Comment 1 Timothy Pearson 2012-05-26 13:25:19 CDT 
I cannot replicate this bug in the latest GIT HEAD for R14.0.
Comment 2 Nikolaus Klepp 2012-08-28 16:30:41 CDT 
As in Slaveks 3.5.13-1 repository the Bug is gone.