[padelsbach]

Description

Fixes failing google.test in PRB-generic-config-parser. As of Oct 30, google started replying with 130 SAN in response to the client handshake in google.test. This causes the test to fail since it does not have memory to store all of them. Fix is to use the -S option on the client app to enable SNI and get a single SAN.

Also fixes the return code from ProcessPeerCerts to properly indicate the failure condition.

Testing

CI, added unit tests

Checklist

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

[Copilot]

🟡 Changes recommended

The test guard still permits --enable-trackmemory, allowing tracked and native allocators to mix during cleanup and cause invalid frees that can crash the test process.

1 open issue

• Exclude track-memory builds from allocator fault injection · New

What changed in this PR

This PR addresses google.test failures caused by large default certificates and corrects memory-allocation error reporting during peer-certificate processing.

Changes:

• Enable SNI in Google connection tests when supported.
• Propagate MEMORY_E when copying the peer certificate fails.
• Add TLS 1.2 and TLS 1.3 regression tests for that failure.

File	Description
tests/​api/​test_ssl_cert.h	Declares and registers the new regression test.
tests/​api/​test_ssl_cert.c	Adds allocation-failure tests for peer-certificate copying.
src/​internal.c	Preserves the certificate-copy memory error.
scripts/​google.test	Detects SNI support and supplies the server name.

_{Review effort: Balanced}

[github-actions]

MemBrowse Memory Report · Explore what changed →

zephyr-frdm_rw612

• FLASH: log_const_area -8 B, rodata -8 B, text +1,576 B (+0.6%, 284,024 B / 67,108,864 B, total: 0% used)

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
• stm32-sim-stm32h753

---

_{Catch memory regressions in CI with MemBrowse. Free for open source.}

[Copilot]

🟡 Changes recommended

Allocator capture is skipped after setup failures, so the unconditional restore can install NULL callbacks and crash cleanup in track-memory builds.

1 open issue

• Capture allocators unconditionally to keep failure cleanup safe · New

1 resolved since last review

• Exclude track-memory builds from allocator fault injection

_{Review effort: Balanced}

[wolfSSL-Fenrir-bot]

Fenrir Automated Review — PR #11968

Scan targets checked: wolfssl-src, wolfssl-bugs
Not reviewed (no scan target covers them): scripts/google.test, tests/api/test_ssl_cert.h
Coverage: 1 of 2 in-scope changed file(s) opened by the reviewer; not opened: tests/api/test_ssl_cert.c

Fenrir result: Approved ✅

No new issues found in the changed files.

Advisory only — this automated result does not count as a GitHub approval.

Review tier: Lite

[philljj]

note: the multi-test failure is unrelated and a known issue being fixed separately.