qsslsocket

Why am I getting runtime errors, with Sockets (TCP/Web) when moved to another thread? Is `QObject::moveToThread()` a synchronous call? [duplicate]

江枫思渺然 提交于 2020-03-05 06:06:53
问题 This question already has answers here : How do I execute QTcpSocket in a different thread? (4 answers) Closed 15 days ago . I am moving some sockets from main thread to worker thread and processing readyRead() , close() , write() etc. on the new thread. Rarely I see below dangerous warning: "QSocketNotifier: Socket notifiers cannot be enabled or disabled from another thread" Usually the execution after this warning results in undefined behaviour (crash / uncaught exception / normal). Have

Why am I getting runtime errors, with Sockets (TCP/Web) when moved to another thread? Is `QObject::moveToThread()` a synchronous call? [duplicate]

[亡魂溺海] 提交于 2020-03-05 06:06:44
问题 This question already has answers here : How do I execute QTcpSocket in a different thread? (4 answers) Closed 15 days ago . I am moving some sockets from main thread to worker thread and processing readyRead() , close() , write() etc. on the new thread. Rarely I see below dangerous warning: "QSocketNotifier: Socket notifiers cannot be enabled or disabled from another thread" Usually the execution after this warning results in undefined behaviour (crash / uncaught exception / normal). Have

Qt: Why is `QAbstractSocket::error(QAbstractSocket::SocketError)` signal not generated when internet is disconnected?

走远了吗. 提交于 2019-12-24 07:01:17
问题 I am trying to achieve a signal when the internet is disconnected for an already connected SSL socket. Here is the way I have derived the QSslSocket : struct CloudSSL::Socket : public QSslSocket { Q_OBJECT public: void ConnectSlots () { connect(this, SIGNAL(readyRead()), this, SLOT(ReceiveData())); connect(this, SIGNAL(disconnected()), this, SLOT(Disconnected())); // *** None of the above or below is invoking when internet disconnects *** connect(this, SIGNAL(error(QAbstractSocket:

Build PyQt5 on Windows with OpenSSL support?

≡放荡痞女 提交于 2019-12-11 04:48:10
问题 I'm trying to build PyQt5 with SSL support but, until now, I have no success at all. What I have done: Rebuild Qt with OpenSSL Support: OK configure.exe -static -debug-and-release -opensource -confirm-license -nomake examples -nomake tests -opengl desktop -platform win32-g++ -openssl-linked OPENSSL_LIBS="-lssleay32 -llibeay32" -I C:\OpenSSL-Win32\include -L C:\OpenSSL-Win32\lib mingw32-make Install SIP: OK python configure.py -p win32-g++ mingw32-make mingw32-make install Install PyQt5: OK

QSslSocket error when SSL is NOT used

岁酱吖の 提交于 2019-11-28 09:14:53
I have noticed this output in two of my Qt applications that use QNetworkRequest to load some data from outside over QNeworkRequest : QSslSocket: cannot resolve TLSv1_1_client_method QSslSocket: cannot resolve TLSv1_2_client_method QSslSocket: cannot resolve TLSv1_1_server_method QSslSocket: cannot resolve TLSv1_2_server_method QSslSocket: cannot resolve SSL_select_next_proto QSslSocket: cannot resolve SSL_CTX_set_next_proto_select_cb QSslSocket: cannot resolve SSL_get0_next_proto_negotiated One example of the request which causes these warnings to appear is QNetworkReply reply = m_nam->get

QSslSocket: cannot call unresolved function

你。 提交于 2019-11-27 16:33:20
问题 I am running Qt 5.7.1 (MSVC 2015, 32 bit) with Qt Creator 4.2.0. I have a problem with QSslSocket . I am getting the following errors: qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method qt.network.ssl: QSslSocket: cannot call unresolved function SSL_CTX_new qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init qt.network.ssl: QSslSocket: cannot call unresolved function ERR_get_error qt.network.ssl: QSslSocket: cannot call unresolved

QSslSocket error when SSL is NOT used

蓝咒 提交于 2019-11-27 02:46:52
问题 I have noticed this output in two of my Qt applications that use QNetworkRequest to load some data from outside over QNeworkRequest : QSslSocket: cannot resolve TLSv1_1_client_method QSslSocket: cannot resolve TLSv1_2_client_method QSslSocket: cannot resolve TLSv1_1_server_method QSslSocket: cannot resolve TLSv1_2_server_method QSslSocket: cannot resolve SSL_select_next_proto QSslSocket: cannot resolve SSL_CTX_set_next_proto_select_cb QSslSocket: cannot resolve SSL_get0_next_proto_negotiated