F-644: fix read of exactly MAX_LEN bytes treated as error

[miyazakh]

Fix "Successful read of exactly MAX_LEN bytes treated as error"
Add test coverage

Depend on : #211 (Fixed)
Depend on : #219

[Copilot]

Pull request overview

Fixes a decryption regression in the non-EVP crypto path where a successful XFREAD() returning exactly MAX_LEN bytes was incorrectly treated as an error, and extends shell test coverage to catch the boundary condition.

Changes:

• Adjust wolfCLU_decrypt() to treat any positive-length XFREAD() result (including exactly MAX_LEN) as success.
• Add an encrypt/decrypt round-trip test (Camellia, non-EVP path) that exercises multi-chunk reads.
• Broaden OCSP interop test log matching for “invalid file” error text across implementations.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
tests/ocsp/ocsp-interop-test.sh	Expands expected error-message pattern matching for invalid certificate file test.
tests/encrypt/enc-test.sh	Adds Camellia round-trip test intended to exercise MAX_LEN read boundary behavior in non-EVP decrypt path.
src/x509/clu_x509_sign.c	Updates preprocessor gating for additional hash enum cases; whitespace-only adjustments nearby.
src/crypto/clu_decrypt.c	Fixes handling of XFREAD() returning exactly MAX_LEN bytes so it is not treated as failure.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.