Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-53758

[Mac OS X] Secure Transport integration forces keychain write access for custom key pair

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Invalid
    • Icon: P2: Important P2: Important
    • None
    • 5.6.0
    • Network: SSL
    • None
    • Mac OS X 10.9
    • macOS

      In the Qt 5.6 the default SSL backend was changed to Secure Transport on the Mac OS platform.

      This has the consequence that when custom certificate and private key is added to QSslConfiguration they are also written to the keychain (due to the SecPkcs12Import call).

      This does not work when application runs as a launchd daemon or for example under 'daemon' account (sudo -u daemon ./testapp).

      The QAbstractSocket::SslInvalidUserDataError error is triggered with "SecPKCS12Import returned no items" description.

        1. qt-ssl-53758.zip
          4 kB
        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            tpochep Timur Pocheptsov
            dremon Dmitry Pankratov
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes