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 473 - konqueror ca cert problems
Summary: konqueror ca cert problems
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdenetwork (show other bugs)
Version: 3.5.12 [Trinity]
Hardware: amd64 Linux
: P5 critical
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2011-05-05 08:46 CDT by Wil Barath
Modified: 2012-10-19 15:14 CDT (History)
2 users (show)

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

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 Wil Barath 2011-05-05 08:46:07 CDT 
After installing TDE 3.5.12 on Maverick, I have the following problems:

1) root ca certificate is not recognized, resulting in every CA being invalid and all sites having invalid certs.  I found this when I tried to go to Trinity donation page, which immediately prompted me saying that PayPal's cert was invalid, which needless to say stopped me cold.

2) inkscape failed to start, with an error already logged on LaunchPad, solution was to delete the gtk config directories in the user's home folders.

3) Konqueror is set to default browser, setting it to Firefox or Chrome is ignored, leaving me with broken HTTPS unless I copy/paste urls from the default Konqueror-spawn across to a browser which works... Tempted to ln -sf /usr/bin/google-chrome /opt/kde3/bin/konqueror but I know that will break the default filemanager etc.

I've tried going through Konqueror's cert setup and selecting the root ca.pem manually, this prompts me 30ish times to tell me that the ca has already been loaded for about 30 distinct CA's, then prompts me whether I want to save the changes, yes had no positive effect.

Any ideas would be appreciated, I'm happy to follow any steps and post back findings.
Comment 1 Timothy Pearson 2011-10-19 01:58:43 CDT 
The root certificate has been repaired for the 3.5.13 release.

Thanks for reporting!