Fix to send record_overflow alert

[embhorn]

Description

Removed the #ifdef HAVE_MAX_FRAGMENT guard so the alert is always sent, matching the unconditional record_overflow and the VERSION_ERROR alert directly above. Also corrected a pre-existing flush-left default: indentation in that block.

Fixes #10791

Testing

New test_tls_record_overflow_alert with three sub-cases that all exercise the fixed line:

1. TLS 1.2 server, pre-handshake — injects a 5-byte oversized record header, asserts the exact cleartext record_overflow alert bytes on the wire.
2. TLS 1.3 server, pre-handshake — same, cleartext byte-exact.
3. TLS 1.3 client, post-handshake — the reported scenario; the encrypted alert is decoded by letting the server read it and checking wolfSSL_get_alert_history returns record_overflow / alert_fatal.

Checklist

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

[Copilot]

Pull request overview

This PR fixes a TLS protocol compliance issue where wolfSSL could terminate on an oversized TLS record without sending the required record_overflow alert, and adds API tests to validate the alert is emitted in both TLS 1.2 and TLS 1.3 scenarios (including post-handshake TLS 1.3 client behavior).

Changes:

• Always send a fatal record_overflow alert when GetRecordHeader() returns LENGTH_ERROR (removes the HAVE_MAX_FRAGMENT guard).
• Add test_tls_record_overflow_alert to validate on-the-wire cleartext alerts pre-handshake and alert history for encrypted alerts post-handshake.
• Register the new test in the API test list.

Reviewed changes

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

File	Description
tests/api/test_tls.h	Adds prototype/registration for the new TLS record overflow alert test.
tests/api/test_tls.c	Adds test_tls_record_overflow_alert with TLS 1.2 + TLS 1.3 pre-handshake cleartext checks and TLS 1.3 post-handshake encrypted alert verification.
src/internal.c	Ensures record_overflow alert is sent on LENGTH_ERROR from record header parsing in all builds.

---

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

[wolfSSL-Fenrir-bot]

Fenrir Automated Review — PR #10795

Scan targets checked: wolfcrypt-rs-bugs, wolfssl-bugs, wolfssl-src

No new issues found in the changed files. ✅

[github-actions]

retest this please

[github-actions]

MemBrowse Memory Report

gcc-arm-cortex-m3

• FLASH: .text +24 B (+0.0%, 121,433 B / 262,144 B, total: 46% used)

gcc-arm-cortex-m4

• FLASH: .text +64 B (+0.0%, 199,116 B / 262,144 B, total: 76% used)
  No memory changes detected for:
• gcc-arm-cortex-m0plus
• 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