[Qt-interest] QtWebKit based browser throws SSL errors while opening https sites (windows only / v2010.01 (open source) )

[Manish Chakravarty]

Oliver,

Thanks for the reply.
I had been through the docs that you mentioned.
What puzzled me is that the same version of the Qt SDK was able to get my
application up and running on the Mac
I did not compile Qt with or without OpenSSL support; I had used the
precompiled libs that Qt Software offers as download.

May be the mac version is picking up the OpenSSL which is installed with OS
X Leopard ( not sure )

As I had mentioned in my original email:
*"I do not get these errors on the Mac ( Leopard ) - these errors are only
seen on windows XP ( unsure about Windows 7/Vista ) "*
*
*
*I guess this would mean that I would have to compile OpenSSL on my windows
machine *and* bundle it when the installer gets shipped out to the customer.
*
Also I will have to look into the legal ramifications of the same.

<digress>
I am not a lawyer, but *if* Apple is able to ship OpenSSL to customers
worldwide ( I am based out of India using the stock OS X Leopard and the
stock Qt SDK ) the  MS should be able to do as well.
</digress>
*
*
Thanks for your time!
Manish Chakravarty

On Mon, Mar 29, 2010 at 6:53 PM, <Oliver.Knoll at comit.ch> wrote:

> Manish Chakravarty wrote on Monday, March 29, 2010 3:06 PM:
>
> > ...
> > QSslSocket: cannot call unresolved function SSLv3_client_method
>
> >From http://qt.nokia.com/doc/4.6/ssl.html:
>
> "By default, an SSL-enabled Qt library dynamically loads any installed
> OpenSSL library at run-time."
>
> This explains the above error: Qt is trying to resolve this symbol
> dynamically, but apparently on your target system there is no such SSL
> library (at least not in the PATH, as it seems).
>
> "Note: Due to import and export restrictions in some parts of the world, we
> are unable to supply the OpenSSL Toolkit with Qt packages. Developers
> wishing to use SSL communication in their deployed applications should
> either ensure that their users have the appropriate libraries installed, or
> they should consult a suitably qualified legal professional to ensure that
> applications using code from the OpenSSL project are correctly certified for
> import and export in relevant regions of the world."
>
> That explains why Qt does not ship with SSL itself (instead it tries to
> dynamically resolve the SSL calls, which apparently fails on your Windows
> machine).
>
> Oh and yes, using Google and the Qt docs helps in such cases, too ;)
>
> Cheers, Oliver
> --
> Oliver Knoll
> Dipl. Informatik-Ing. ETH
> COMIT AG - ++41 79 520 95 22
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-interest
>



-- 
Manish Chakravarty
Blog: http://manish-chaks.livejournal.com/
LinkedIn: http://www.linkedin.com/in/manishchakravarty
Twitter: http://twitter.com/ManishChaks
Facebook: http://www.facebook.com/manish.chakravarty
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20100330/9ec762f9/attachment.html