Hi,
I must have misunderstood the report... In any case, I filtered out expired
certificates and now everything's back to work.
In case anyone may be interested, here's the code I used for filtering:
https://gist.github.com/2462852
Thanks for all the help,
Ynon
On 18 April 2012 13:32, Thiago
On quarta-feira, 18 de abril de 2012 07.36.52, ynon perek wrote:
> I hope not. Is there an easy way to check ?
>
> I tried both this bundle (from cacert.org):
> http://www.cacert.org/index.php?id=3
>
> And this one (extracted from mozilla through curl's website):
> http://curl.haxx.se/docs/caextrac
I hope not. Is there an easy way to check ?
I tried both this bundle (from cacert.org):
http://www.cacert.org/index.php?id=3
And this one (extracted from mozilla through curl's website):
http://curl.haxx.se/docs/caextract.html
On 17 April 2012 23:00, Thiago Macieira wrote:
> On terça-feira,
On terça-feira, 17 de abril de 2012 22.46.08, ynon perek wrote:
> Will need to check for parsing errors and post back later. Could it be
> related to this bug:
> https://bugreports.qt-project.org/browse/QTBUG-14520 ?
Did you add expired certificates to your bundle?
--
Thiago Macieira - thiago.maci
Hi,
Code that gets the error is simple:
void RemoteWLS::logSslError( const QList & errors )
{
QLOG_INFO() << "Ssl Error: " << errors;
}
And when creating the request:
QObject::connect(reply, SIGNAL(sslErrors( const QList &)),
this, SLOT(logSslError( const QList &)))
On terça-feira, 17 de abril de 2012 08.52.18, ynon perek wrote:
> Hi All,
> I'm trying to get QtWebkit to work nicely with ssh. It usually does so
> out-of-the-box but the problem is for some machines it does not.
>
> On the problematic machines, an SSL error signal is sent.
> If I print the errors
Hi All,
I'm trying to get QtWebkit to work nicely with ssh. It usually does so
out-of-the-box but the problem is for some machines it does not.
On the problematic machines, an SSL error signal is sent.
If I print the errors to a log file I get the error code: QSslError::NoError
I suspect it had s