TLS 1.3 PHA with OCSP Stapling

[kojo1]

Description

1. CertificateRequest is missing the status_request extension.
   When the server triggers PHA via wolfSSL_request_certificate(),
   the status_request extension is suppressed, so the server cannot
   ask the client to staple OCSP information for its certificate
   (RFC 8446 §4.2 / §4.4.2.1).

2. The PHA-side client Certificate is not subject to the
   server's OCSP-status check. ProcessPeerCerts() only entered the
   OCSP path for WOLFSSL_CLIENT_END, so the OCSP staple supplied by
   the client was never validated.

3. fix Multiple PSA

Fixes zd#21555, zd#21814

Testing

added test_tls13_pha_status_request

Checklist

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

[github-actions]

MemBrowse Memory Report

gcc-arm-cortex-m4-openssl-compat

• FLASH: .text +64 B (+0.0%, 771,212 B / 1,048,576 B, total: 74% 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-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

[kojo1]

retest this please

[kojo1]

retest this please

[kojo1]

Retest this please.

[dgarske]

Please resolve merge conflicts

[dgarske]

Jenkins retest this please: "Build 'wolfSSL/PRB-fips-repo-and-harness-test-v3-part2' failed with result: FAILURE"

[kojo1]

Merge conflicts resolved.
Added fix for repeated PHA over write_dup (zd#21814).

Thank you for your review in advance.

[dgarske]

Jenkins retest this please. History lost

[Copilot]

Pull request overview

This PR fixes TLS 1.3 Post-Handshake Authentication (PHA) interoperability and OCSP stapling behavior by ensuring status_request is correctly carried on PHA CertificateRequest and that the server performs OCSP-status checking on the client certificate received during PHA.

Changes:

• Emit TLS 1.3 status_request in CertificateRequest during PHA with the correct empty extension body, and ensure size/write paths agree.
• Extend OCSP validation logic to apply to client certificates received post-handshake (PHA) while tolerating missing staples unless “must-staple” is enforced.
• Add a regression test covering TLS 1.3 PHA + status_request flow and transcript synchronization across read/write dup sides.

Reviewed changes

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

Show a summary per file

File	Description
wolfssl/internal.h	Adds write-dup state to publish post-PHA transcript hash to keep read/write sides synchronized across PHA rounds.
src/ssl.c	Publishes post-PHA transcript hash from write side to read side; frees new synced-hash state during cleanup.
src/tls13.c	Recreates/initializes OCSP CSR state for client-side PHA, reuses request slots, frees prior response buffers, and enables OCSP response setup on client during PHA.
src/tls.c	Ensures status_request is present in TLS 1.3 CertificateRequest and encoded with empty body; adds NULL-guarding for CSR size/write helpers.
src/internal.c	Runs OCSP leaf revocation logic for server-side PHA and treats missing/empty client staple as non-fatal unless must-staple is required.
tests/api/test_tls13.h	Registers new TLS 1.3 API test declaration.
tests/api/test_tls13.c	Adds test_tls13_pha_status_request regression test for PHA + status_request + empty-staple tolerance.

---

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