Hi Adam, On Thu, May 5, 2011 at 20:57, [email protected] <[email protected]> wrote: > > On 05/04/2011 08:39 PM, Alexander Bokovoy wrote: >> >> There seem to be some misconfiguration of SSL setup at meego.com. I >> >> tried with QtWebkit and it also unable to reach and render it. >> >> Looking into a network trace I can see that Firefox 4 talks TLSv1 to >> meego.com while QtWebkit uses SSLv3. >> >> > This actually is how its intended, bugs.meego.com is a TLS-SNI website > (SSL named Vhosting): > (read about it here: http://en.wikipedia.org/wiki/Server_Name_Indication). > > The reason its TLS-SNI primarily is that we want to be good citizens and > conserve IPs. We also can't get more to dedicate to each SSL site. > > If you connect to some of our services you'll get a self-signed SSL > certificate when TLS-SNI support is not available in your user-agent. If > you hit this URL you'll be served a help page that talks about this: > > https://140.211.166.236/TLS-SNI.html > > Primarily the complaints about this have come from people using Internet > Explorer on Windows XP which led us to ask, why are you accessing our > site with such an old software stack? Qt Networking of 4.7 is not supporting TLS SNI on all platforms. See other mails in the thread.
This primarily affects my RSS fetcher but a work around has been already found.(see the other mail) and Thiago said it is fixed in Qt 4.8 by supporting SNI. > meego.com has a dedicated IP and does not use TLS-SNI for its SSL. Nevertheless, it behaves the same way: when prompted to communicate with SSLv3, it aborts handshake. -- / Alexander Bokovoy _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
