From the original bug report I'm linking to here it appears that file-based keychains finally stopped working on macOS 15, giving the reporter "SslInvalidInternalData". Their investigation shows that removing QT_SSL_USE_TEMPORARY_KEYCHAIN fixed their issue with QSslSocket. But this type of error we emit (with SecureTransport backend) only if we fail to create SecIdentityRef from cert/private key (and SecPKCS12Import essentially relies on file-based keychain if it's enabled with env. variable). Thus it makes sense to test, issue a warning at runtime and document this 'new' behavior and what a user is supposed to do to avoid their server app ( ? ) from being blocked by keychain access popup (which was the reason we introduced temporary keychains).