Trolltech Home | Qt4-preview-feedback Home | Recent Threads | All Threads | Author | Date
All threads index page 1

Qt4-preview-feedback Archive, May 2007
Default protocol for QSslSocket


Message 1 in thread

I've just spent some time debugging a handshake problem with QSslSocket
which was caused by the default protocol being SSLv3 only (I now realise
this is documented so a clear case of RTFM on my part :) ).  I presume this
is the most secure option so I commend this, but as a default it would
appear to limit interoperability as I couldn't get the Qt 3 QtSslSocket
Solution to connect to my server using it, nor would KMail from the current
KDE 3.  In view of this, perhaps there's a case for changing the default to
QSslSocket::AnyProtocol.

Failing that, at least I might save somebody else some time by pointing out
you can use QSslSocket::setProtocol(QSslSocket::AnyProtocol) to
simultaneously support TLSv1, SSLv2 and SSLv3.

-- 
 [ signature omitted ] 

Message 2 in thread

Mark Sawle wrote:
> KDE 3.  In view of this, perhaps there's a case for changing the default
> to QSslSocket::AnyProtocol.

If AnyProtocol didn't include SSLv2, I would concur. Unfortunately it does,
however, so the most common protocol happens to be SSLv3. It's an
unfortunate, but necessary, default value.

-- 
 [ signature omitted ] 

Message 3 in thread

Andreas Aardal Hanssen <ahanssen@xxxxxxxxxxxxx> wrote:

> Mark Sawle wrote:
> > KDE 3.  In view of this, perhaps there's a case for changing the default
> > to QSslSocket::AnyProtocol.
> 
> If AnyProtocol didn't include SSLv2, I would concur. Unfortunately it
> does, however, so the most common protocol happens to be SSLv3. It's an
> unfortunate, but necessary, default value.

Fair enough. :)

-- 
 [ signature omitted ]