Rust wrapper: rsa: fix sha224/sha384 cfg guards for hash type constants

[holtrop-wolfssl]

Description

Rust wrapper: rsa: fix sha224/sha384 cfg guards for hash type constants

Fixes F-10088.

Testing

How did you test?

Checklist

• added tests
• updated/added doxygen
• updated appropriate READMEs
• Updated manual and documentation

[Copilot]

🟡 Changes recommended

The build script uses cargo::rustc-check-cfg (extra :), which Cargo will not parse as a build-script directive, preventing rustc-check-cfg validation from working.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Fixes feature-gating in the Rust wolfCrypt RSA wrapper so hash-type constants are only exposed when the corresponding hashes are actually enabled, aligning the Rust API surface with the underlying wolfSSL build configuration (Fixes F-10088).

Changes:

• Corrected #[cfg] guards for RSA hash type constants (SHA-224 and SHA-384) in the Rust wrapper.
• Refactored build-script cfg probing to support conditional cfg enabling (check_cfg_if) and improved SHA-512/224 + SHA-512/256 feature detection.
• Minor comment punctuation normalization in build.rs.

File summaries

File	Description
wrapper/rust/wolfssl-wolfcrypt/src/rsa.rs	Fixes SHA-224/SHA-384 cfg guards for RSA hash-type constants so they match the actual enabled hashes.
wrapper/rust/wolfssl-wolfcrypt/build.rs	Improves cfg detection logic (adds has_symbol/check_cfg_if) and tightens SHA-512/224 + SHA-512/256 related gating; minor comment tweaks.

Review details

Suppressed comments (1)

wrapper/rust/wolfssl-wolfcrypt/build.rs:509

• cargo::rustc-check-cfg has an extra ':' and won’t be recognized by Cargo build-script parsing (Cargo expects cargo:...). As written, the rsa_const_api cfg name won’t be registered for check-cfg validation.

    println!("cargo::rustc-check-cfg=cfg(rsa_const_api)");

• Files reviewed: 2/2 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

MemBrowse Memory Report

No memory changes detected for:

• gcc-arm-cortex-m0plus
• gcc-arm-cortex-m3
• gcc-arm-cortex-m4
• gcc-arm-cortex-m4-baremetal
• gcc-arm-cortex-m4-crypto-only
• gcc-arm-cortex-m4-dtls13
• gcc-arm-cortex-m4-min-ecc
• gcc-arm-cortex-m4-openssl-compat
• gcc-arm-cortex-m4-pkcs7
• gcc-arm-cortex-m4-pq
• gcc-arm-cortex-m4-rsa-only
• gcc-arm-cortex-m4-sp-math
• gcc-arm-cortex-m4-tls12
• gcc-arm-cortex-m4-tls13
• gcc-arm-cortex-m7
• gcc-arm-cortex-m7-pq
• gcc-arm-cortex-m7-tls13
• linuxkm-pie
• linuxkm-standard
• stm32-sim-stm32h753

[holtrop-wolfssl]

retest this please (build removed)

[holtrop-wolfssl]

retest this please (ERROR: script returned exit code 5)