Yes, this is why I implemented https://codereview.qt-project.org/#/c/80470/
Rich.
On 21 October 2014 23:20, Thomas Lübking thomas.luebk...@gmail.com wrote:
On Dienstag, 21. Oktober 2014 21:24:33 CEST, Dawit A wrote:
I think this whole problem came about as a result of a misunderstanding?
On Mittwoch, 22. Oktober 2014 22:11:56 CEST, Richard Moore wrote:
Yes, this is why I implemented https://codereview.qt-project.org/#/c/80470/
Thanks, I guess you can close
https://bugreports.qt-project.org/browse/QTBUG-42112 then.
Cheers,
Thomas
Yeah, though sadly since it required new symbols I couldn't backport that
change. :-(
Rich.
On 22 October 2014 22:05, Thomas Lübking thomas.luebk...@gmail.com wrote:
On Mittwoch, 22. Oktober 2014 22:11:56 CEST, Richard Moore wrote:
Yes, this is why I implemented
On Montag, 20. Oktober 2014 01:13:35 CEST, Thiago Macieira wrote:
On Sunday 19 October 2014 18:14:36 Thomas Lübking wrote:
On Sonntag, 19. Oktober 2014 16:35:35 CEST, Dawit A wrote: ...
This is looking like a Qt bug instead. Can you investigate
QSslSocket instead?
This is the list of
I think this whole problem came about as a result of a misunderstanding?
More specifically a misreading of what the protocol information in the
cipher itself was meant to convey. The OpenSSL documentation for
SSL_CIPHER_get_version,
http://www.openssl.org/docs/ssl/SSL_CIPHER_get_name.html, states
On Dienstag, 21. Oktober 2014 21:24:33 CEST, Dawit A wrote:
I think this whole problem came about as a result of a misunderstanding?
[...]
So the protocol string in the cipher is merely a historical information as
to when that cipher was first defined and not meant to convey the current
On Montag, 20. Oktober 2014 01:13:35 CEST, Thiago Macieira wrote:
On Sunday 19 October 2014 18:14:36 Thomas Lübking wrote:
On Sonntag, 19. Oktober 2014 16:35:35 CEST, Dawit A wrote: ...
This is looking like a Qt bug instead. Can you investigate
QSslSocket instead?
Hmmm... checking this
Both the protocol and protocolString methods in QSslCipher return a
different value than what is expected. For example, in Qt 4.8 if you set
the protocol in QSslSocket to QSsl::TlsV1 and connect to blog.mozilla.org
port 443, you get the following output from QSslCipher:
QSslSocket Information:
On Sunday 19 October 2014 18:14:36 Thomas Lübking wrote:
On Sonntag, 19. Oktober 2014 16:35:35 CEST, Dawit A wrote:
protocolString: SSLv3
...
However if one uses openssl directly, the following information is
returned:
$ openssl s_client -connect blog.mozilla.org:443
New,