Bug 287216

Summary: Certificate handling with Server Name Indication (SNI) does not work correctly
Product: [Frameworks and Libraries] kio Reporter: jda <_jeroen_>
Component: ksslAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: adawit
Priority: NOR    
Version: 4.7   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:

Description jda 2011-11-22 01:03:24 UTC
Version:           4.7.2 (using KDE 4.7.2) 
OS:                Linux

Connecting via https to a host (for example 2.testhost.lan (apache is configured with 1.testhost.lan as primary host, both hosts have unique and specific SSL keys installed)) requiring SNI results in warnings and wrong certificates being used.

The error message:
'The server failed the authenticity check (2.testhost.lan).

The certificate does not apply to the given host'

On examination the certificate of the 'primary' host (1.testhost.lan in the example) is presented.

Continuing results in display of the contents of host 1 (but on some server configurations apparently the contents of 2 (2.testhost.lan) are displayed, but with the certificate and encryption settings of host 1)

When using SNI host and certificate/encryption settings should match.

Reproducible: Always

Steps to Reproduce:
Connect to an SNI enabled site using multiple hosts, for example
https://alice.sni.velox.ch/

Actual Results:  
on the velox.ch test site the primary host&certificate is used, I have run into sites which display the secondary sites using the primary site's certifiate however.

Expected Results:  
Connection established to the correct host using the correct certificate

For people concerned about SNI-privacy concerns one could add an option to turn it off.

probably related to https://bugs.kde.org/show_bug.cgi?id=122433
Comment 1 Dawit Alemayehu 2012-08-19 19:28:46 UTC
Since 304212 is effectively the same report and other bug reports have been marked duplicate of instead of this older one, I am going to mark this as duplicate of the aforementioned bug report.

*** This bug has been marked as a duplicate of bug 304212 ***