@forca maybe you need to do some additional steps

From QSslSocket documentation:

Describes the peer verification modes for QSslSocket. The default mode is AutoVerifyPeer, which selects an appropriate mode depending on the socket's QSocket::SslMode.
QSslSocket::QueryPeer 1
QSslSocket will request a certificate from the peer, but does not require this certificate to be valid. This is useful when you want to display peer certificate details to the user without affecting the actual SSL handshake. This mode is the default for servers. Note: In Schannel this value acts the same as VerifyNone.

And looking at this QWebEnginePage browser example, check the Downloading Favicons code snippet, which may help you accessing the underlying QSslSocket

@bublee_jessie And what is the problem? On the server side check the client IP which is trying to connect and only accept connection if correct IP and not connected yet.

@Prince_0912 Thank you for your guidlines

@VRonin said in Need Help with getting a slot executed in the correct thread:

the default implementation of QThread::run starts an event loop so if you use the method described in that link everything will work out of the box

Indeed it does! Thanks!

@Allerknappe should your question better suited for AWS support team? or cloud forum? It seems not related to Qt itself.
Anyway, from little experience with a (non Qt) REST server running in AWS, in that case the server was configured with "internal" IP and then the AWS security team forwarded the proper port(s) so the solution could be available from outside.

@ganeshkbhat Allowing to load and run 3rd C++ inside your main applications's process is very dangerous and we have not found any easy way to sandbox C++ so far, only just have a few ideas worth trying. I've described this issue here in a little more detail.

Frankly, I forgot about it.

Then it also depends also on what tools fits best your needs. There's no silver bullet that will cover everything you need.

Also limiting yourself to only one language is not a good idea in the long run. There are good and bad things in every language thus knowing more than one allows to have a better grasp at what can be done, how easy/hard the maintenance would be etc.

The handshake is the process that establishes the secure connection, in Qt QSslSocket::connectToHostEncrypted and QSslSocket::startServerEncryption take care of the handshake. The "Hello Word" sent across is just normal TCP communication that could be done even without encryption (i.e. using QTcpSocket)

How about the Fortune example?

Cheers.

@mrjj Com_Network is my own class which I use for Communication between Client and Server. Ok, I will give it a try.

@SGaist Hi, However is in my plan.

Yes, that's a standard approach that has worked quiet well already for a long time :-)