mirror of https://github.com/wolfSSL/wolfssh.git
9731cfe250
The dependency assertion checked only that wolfssl was present with a DEPENDS_ON edge, never that the recorded version matched WOLFSSL_DIR, so the SBOM could attest a version wolfSSH was not built against and still pass. Compare versionInfo against the tree. That assertion alone would not have caught it: the runner installs wolfssl from the same tree it passes as WOLFSSL_DIR, so pkg-config and wolfssl/version.h always agree and a wrong source is indistinguishable from a right one. Add a step that forces them apart -- a stub pkg-config reports a sentinel version, and a distclean'd copy of the tree has no generated version.h, so the configure.ac fallback is the only route to a correct answer. Reverting the recipe fix makes this step fail with the sentinel, and the fallback path now has CI coverage it lacked. |
||
|---|---|---|
| .. | ||
| code-coverage.yml | ||
| codespell.yml | ||
| coverity-scan-fixes.yml | ||
| cppcheck.yml | ||
| interop-mlkem.yml | ||
| multi-compiler.yml | ||
| network-contention-test.yml | ||
| os-check.yml | ||
| paramiko-sftp-test.yml | ||
| sanitizer.yml | ||
| sbom.yml | ||
| scp-test.yml | ||
| sftp-test.yml | ||
| singlethread-check.yml | ||
| sshd-test.yml | ||
| test-fatfs.yml | ||
| tpm-ssh.yml | ||
| windows-check.yml | ||
| windows-sftp.yml | ||
| x509-interop.yml | ||
| zephyr.yml | ||