On 06/06/15 15:26,
development-bounces+lars.knoll=theqtcompany@qt-project.org on behalf of
Thiago Macieira
development-bounces+lars.knoll=theqtcompany@qt-project.org on behalf of
thiago.macie...@intel.com wrote:
On Saturday 06 June 2015 14:22:20 Giuseppe D'Angelo wrote:
Il
On Saturday 06 June 2015 14:22:20 Giuseppe D'Angelo wrote:
Il 06/06/2015 13:27, Thiago Macieira ha scritto:
Then why do we need them in QSslSocket?
Technically they are be needed there, indeed, but I didn't want to cause
an API asymmetry with the other functions for ciphers, certificates
Il 06/06/2015 11:20, Thiago Macieira ha scritto:
These should be in QSslConfiguration, not QSslSocket.
They're in both, just like ciphers, certificates etc.
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Software Engineer
KDAB (UK) Ltd., a KDAB Group company | Tel: UK +44-1625-809908
KDAB
Il 06/06/2015 13:27, Thiago Macieira ha scritto:
Then why do we need them in QSslSocket?
Technically they are be needed there, indeed, but I didn't want to cause
an API asymmetry with the other functions for ciphers, certificates and
so on, that's all.
--
Giuseppe D'Angelo |
On Saturday 06 June 2015 11:30:39 Giuseppe D'Angelo wrote:
Il 06/06/2015 11:20, Thiago Macieira ha scritto:
These should be in QSslConfiguration, not QSslSocket.
They're in both, just like ciphers, certificates etc.
Then why do we need them in QSslSocket?
--
Thiago Macieira -
On Friday 05 June 2015 10:11:29 Frederik Gladhorn wrote:
+// EC settings.
+QVectorQSslEllipticCurve ellipticCurves() const;
+void setEllipticCurves(const QVectorQSslEllipticCurve curves);
+static void setDefaultEllipticCurves(const QVectorQSslEllipticCurve
curves); +static
diff --git a/src/network/access/qabstractnetworkcache.h b/src/network/access/qabstractnetworkcache.h
index b563090..352daa9 100644
--- a/src/network/access/qabstractnetworkcache.h
+++ b/src/network/access/qabstractnetworkcache.h
@@ -37,6 +37,7 @@
#include QtCore/QObject
#ifndef QT_NO_SSL
