Removes the wolfSSL-specific QSKIP hunk for Qt certificate unit test#348
Open
miyazakh wants to merge 1 commit into
Open
Removes the wolfSSL-specific QSKIP hunk for Qt certificate unit test#348miyazakh wants to merge 1 commit into
miyazakh wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the vendored Qt 5.15.18 wolfSSL integration patch by removing an obsolete wolfSSL-specific QSKIP guard for the tst_QSslCertificate::nulInSan() unit test, so the test is no longer conditionally skipped based on behavior that no longer exists in current wolfSSL.
Changes:
- Removes the
QT_NO_WOLFSSL-guardedQSKIPblock previously added tonulInSan()within the patch, eliminating dead/misleading skip logic. - Leaves the rest of the patch intact (other wolfSSL-related adjustments remain unchanged).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Removes the wolfSSL-specific
QSKIPhunk fortst_QSslCertificate::nulInSan()fromqt/wolfssl-qt-51518-full.patch. It is no longer needed and causes the test to be skipped instead of passed.Background
nulInSan()loads a certificate with a NUL byte embedded in a SANdNSNameentry and verifies it parses to a non-emptycertList.DecodeGeneralNameCheckChars()inwolfcrypt/src/asn.c, which rejects SAN entries containing NUL bytes at parse time (ASN_PARSE_E). This madecertListempty, so the Qt patch added aQSKIPguard to avoid a hard failure.e1a2ba3b/ merged as7dd269f) removedDecodeGeneralNameCheckChars(), explicitly stopping the rejection of embedded-NUL IA5String SAN values at parse time. Certificates with embedded NUL bytes now parse successfully again,certListis no longer empty, and theQSKIPguard never triggers — the test now runs and passes on its own.Keeping the guard is harmless functionally, but it's dead code carried over from a wolfSSL behavior that no longer exists, and its presence is misleading when reading the patch.
Change
Drop the following hunk from
qt/wolfssl-qt-51518-full.patch:Testing
Built Qt 5.15.18 with
-wolfssl-linkedagainst current wolfSSL master (a4aab71ff, post-PR#10793) and ran the test directly: