From: Manuel Nickschas Date: Mon, 24 Mar 2014 21:28:16 +0000 (+0100) Subject: QSslCertificate::isValid() no longer exists in Qt5 X-Git-Tag: 0.11.0~66 X-Git-Url: https://git.quassel-irc.org/?p=quassel.git;a=commitdiff_plain;h=5366497b8816bf13934179556ee63bf62e7cf162 QSslCertificate::isValid() no longer exists in Qt5 Qt4's isValid() checked for the date range and if the cert is blacklisted. In Qt5, these two checks need to be done explicitly. --- diff --git a/src/core/sslserver.cpp b/src/core/sslserver.cpp index 87ca4522..997578a3 100644 --- a/src/core/sslserver.cpp +++ b/src/core/sslserver.cpp @@ -123,9 +123,22 @@ bool SslServer::setCertificate(const QString &path) quWarning() << "SslServer:" << qPrintable(path) << "contains no certificate data"; return false; } - if (!_cert.isValid()) { - quWarning() << "SslServer: Invalid certificate (most likely expired)"; - // We allow the core to offer SSL anyway, so no "return false" here. Client will warn about the cert being invalid. + + // We allow the core to offer SSL anyway, so no "return false" here. Client will warn about the cert being invalid. + const QDateTime now = QDateTime::currentDateTime(); + if (now < _cert.effectiveDate()) + quWarning() << "SslServer: Certificate won't be valid before" << _cert.effectiveDate().toString(); + + else if (now > _cert.expiryDate()) + quWarning() << "SslServer: Certificate expired on" << _cert.expiryDate().toString(); + + else { // Qt4's isValid() checks for time range and blacklist; avoid a double warning, hence the else block +#if QT_VERSION < 0x050000 + if (!_cert.isValid()) +#else + if (_cert.isBlacklisted()) +#endif + quWarning() << "SslServer: Certificate blacklisted"; } if (_key.isNull()) { quWarning() << "SslServer:" << qPrintable(path) << "contains no key data";