Bug 147491 - New Verisign signed certificates are not recognized as valid
Summary: New Verisign signed certificates are not recognized as valid
Status: RESOLVED LATER
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Brad Hards
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-03 12:28 UTC by Peter Soetens
Modified: 2010-03-08 06:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Soetens 2007-07-03 12:28:19 UTC
Version:           3.5.6 (using KDE 3.5.6, Kubuntu (feisty) 4:3.5.6-0ubuntu14)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.20-15-generic

A recently issued Verisign signed certificate on https://www.fmtc.be is not recognised as valid by konqueror. It says: 

Certificate State : Certificate signing authority is unknown or invalid.

It seems the Organisational unit ending in ... (c)05 is not known by konqueror. Looking at the SSL configuration, only the units ending in ... (c)00 are known.
Comment 1 Duncan 2007-10-02 15:55:51 UTC
I'm running into this issue here as well, also with my bank, Bank of America.  Here's their login page, which shows the issue.  I've already confirmed other people get the same problem too; you don't have to have an account to see it.

https://onlineid.bankofamerica.com/cgi-bin/sso.login.controller?state=AZ

It appears to be a (c)05 certificate in my case as well.  The bank just updated in August (their cert valid Aug 20, 2007 thru Aug 19, 2008, but that's not the signing cert).

Meanwhile, that confirmation from a few others is enough for me to believe I'm not getting hit by a MitM attack, so I can accept the bank's certificate and continue as usual.

Duncan
Comment 2 Rowan Collins 2008-04-07 19:07:45 UTC
As a web developer, I just had this with one of our sites, and it turned out that we were missing an "intermediate" certificate which has to be added to the site's configuration (with an "SSLCertificateChainFile" Apache statement) alongside the usual key and certificate files. 

No warnings were shown in Internet Explorer 7, but Firefox 2 and 3beta5 both said the issuer was not recognised. It may be worth passing this on to the sites mentionned here, in case they have the same mis-configuration.

Cheers,
Rowan Collins
Comment 3 Jaime Torres 2008-06-28 10:00:13 UTC
It works for me in konqueror 4.1b2 svn trunk r813735.
None of the sites shows any warnings about ssl certificates and the pages are rendered well.
Comment 4 Brad Hards 2010-03-08 06:52:18 UTC
This doesn't look like it is being requested by the CA.