On Thu, Nov 22, 2018 at 8:52 PM Konstantin Shegunov <[email protected]> wrote:
> No, same error. I'm not 100% the problem is strictly the client > It turned out it isn't. The server didn't manifest the certificate at all due to an error on my part - I gave it the wrong file path. To add insult to injury QSslSocket::setLocalCertificate silently succeeds whatever path you give it; no return status, no debug warning, no ssl error, no nothing. Still, thank you Mårten for the comment, I appreciate it nonetheless.
_______________________________________________ Interest mailing list [email protected] https://lists.qt-project.org/listinfo/interest
