Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. openssl version error - need to detect programmatically
QtWS25 Last Chance

openssl version error - need to detect programmatically

Scheduled Pinned Locked Moved General and Desktop
qsslsocketopenssl
3 Posts 2 Posters 1.5k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    Jeff Andle
    wrote on 16 Jun 2016, 00:17 last edited by
    #1

    I know why I get this error - the program was compiled with one version (1.0.2d) but the libraries were 1.0.2c. The console logs show the issue (it's embedded ARM, not that this matters),

    QSslSocket: cannot call unresolved function SSLv23_client_method
    QSslSocket: cannot call unresolved function SSL_CTX_new
    QSslSocket: cannot call unresolved function SSL_library_init
    QSslSocket: cannot call unresolved function ERR_get_error
    QSslSocket: cannot call unresolved function ERR_get_error

    but my program just knows that a network operation timed out. I'd like to know how to detect this clash and disable the dependent feature (email) as well as display an alert to the user.

    "Network operation timed out"

    pretty sure the error happens here:

            ((QSslSocket*) socket)->startClientEncryption();
    
            if (!((QSslSocket*) socket)->waitForEncrypted(connectionTimeout)) {
                qDebug() << ((QSslSocket*) socket)->errorString();
                emit smtpError(ConnectionTimeoutError);
                return false;
            }
    
    1 Reply Last reply
    0
    • J Offline
      J Offline
      Jeff Andle
      wrote on 29 Jun 2016, 17:02 last edited by
      #2

      any suggestions?

      1 Reply Last reply
      0
      • F Offline
        F Offline
        flart
        wrote on 30 Dec 2016, 13:40 last edited by flart
        #3

        https://www.openssl.org/policies/releasestrat.html
        "Minor releases that change the last digit, e.g. 1.0.1 vs. 1.0.2, can and are likely to contain new features, but in a way that does not break binary compatibility."

        So I don't believe what "1.0.2d vs 1.0.2c" itself causes a problem.

        1 Reply Last reply
        2

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved