wolfssl: fix broken build

[tc-agent]

Summary

The wolfssl OSS-Fuzz build has been failing since the 2026-05-19 build run; the last successful build was 2026-05-18 (build history: https://oss-fuzz-build-logs.storage.googleapis.com/index.html#wolfssl).

Root cause

wolfSSL/wolfssl#10460, merged 2026-05-18, changed the public wolfCrypt MD2 and MD4 API from returning void to returning int (wc_InitMd2 / wc_Md2Update / wc_Md2Final and the MD4 equivalents).

The Cryptofuzz wolfCrypt module instantiates its Digest<> wrappers for MD2 and MD4 with the Init_Void / DigestUpdate_Void / DigestFinalize_Void template variants. After the signature change those template arguments no longer match the wolfCrypt function pointers, so compilation fails:

module.cpp:680:9: error: no matching constructor for initialization of
  'Digest<Md2, 16, Init_Void<Md2>, DigestUpdate_Void<Md2>, DigestFinalize_Void<Md2>>'

Fix

build.sh patches the MD2/MD4 Digest<> instantiations in the Cryptofuzz checkout to use the *_Int template variants, which Cryptofuzz already provides and uses for the other int-returning digest APIs (MD5, SHA-*, RIPEMD, …). The patch is applied with sed, consistent with the Cryptofuzz patching build.sh already performs.

With this change the build compiles cleanly and produces all 22 fuzz targets.

References

• Fuzz Introspector (baseline ~31.81% line coverage): https://introspector.oss-fuzz.com/project-profile?project=wolfssl
• Build history: https://oss-fuzz-build-logs.storage.googleapis.com/index.html#wolfssl
• Upstream API change: Static analysis fixes/improvements for SECO, devcrypto, ARIA, MD4, MD2 wolfSSL/wolfssl#10460

[github-actions]

Fuzzing Coverage Report

Tested: project wolfssl · base 5339266 → head 8b35c90 · 300s total fuzz budget · updated 2026-05-27 22:35 UTC · workflow run

Metric	Before	After	Delta
Static reachability	>45m	>45m	—

_{Δ = (after − before) / before, to accommodate that denominators may change. "new" when before is 0; "deleted" when after is 0.}