Comment 2 for bug 334191

Version: (using KDE 4.0.4)
Installed from: Fedora RPMs
OS: Linux

All actions below are done using Konqueror 4.0.4 on Fedora 9.

Visiting https://www.verisign.com/ loads the page just fine with no warning messages (though I can't figure out how to display the certificate information about the loaded page).

However, visiting https://www.sslcertificaten.nl/, which has a chained certificate loads with an authenticity check warning (See authenticity.png screenshot). Clicking details shows the certificate chain, but the "Trust" section simply says "TODO" (see chain1.png and chain2.png screenshots).

Visiting http://www.dragonstrider.com/security/cacert.pem brings up the certificate viewer, and it loads the valid dates, key and signature information just fine, but the common name stuff for both the key and the signer are using dummy values of "Acme Co." and "Acme Sundry Products Company", etc. (See cadetails.png screenshot).

Clicking Import on that screen tells you that the import was successful, but mentions "KDE Control Center" to manage certificates (See acceptedimport.png screenshot).

Clicking the "Crypto Manager" button brings up a window entitled "Crypto - KDE Control Module". A few of the tabs in this window show dummy text similar to the key info page (See cryptomanager1&2.png screenshots). Click over to Signers, and the list is empty including of Verisign's root Certificate, which supposedly is valid, or the recently imported dragonstrider certificate (see cryptomanager3.png screenshot). Clicking import here, and then attempting to import the CACert.org root certificate adds the certificate to the list, but with no details about it (see cryptomanager4.png screenshot). Click OK to close the window, and bring it up again, and the signer's list is again empty.

Kleopatra 3.5.9 on the same system seems to be able to import CA Root Certificates just fine.