[openssl/openssl] 2d3e26: x509: add ocsptest for the OCSP stapled-response v...

"'Jakub Zelenka' via openssl-commits" <[email protected]> Mon, 13 Jul 2026 08:06:36 -0700
Newsgroups gmane.comp.encryption.openssl.cvs
Message-ID <openssl/openssl/push/refs/heads/master/[email protected]>
  Branch: refs/heads/master
  Home:   https://github.com/openssl/openssl
  Commit: 2d3e267b2b035859b1da38644721afef8d88d792
      https://github.com/openssl/openssl/commit/2d3e267b2b035859b1da38644721afef8d88d792
  Author: Jakub Zelenka <[email protected]>
  Date:   2026-07-13 (Mon, 13 Jul 2026)

  Changed paths:
    M test/build.info
    A test/ocsptest.c
    M test/recipes/80-test_ocsp.t

  Log Message:
  -----------
  x509: add ocsptest for the OCSP stapled-response verification path

Add test/ocsptest.c, exercising check_cert_ocsp_resp() in x509_vfy.c
through X509_verify_cert() with X509_V_FLAG_OCSP_RESP_CHECK and
responses attached via X509_STORE_CTX_set_ocsp_resp(). This path was
previously only covered indirectly through the TLS multi-stapling
tests in sslapitest.c.

The test builds signed OCSP responses at run time from a flat
root -> leaf PKI (the root is both the trust anchor and the authorized
responder), and covers the good, grace-period, non-successful status,
expired, no-response, and wrong-certificate cases, plus a mfail run
over the success path. The PKI is generated by the test-tools ocsptest
command.

Assisted-by: Claude:claude-opus-4-8

Reviewed-by: Daniel Kubec <[email protected]>
Reviewed-by: Tomas Mraz <[email protected]>
MergeDate: Mon Jul 13 15:04:59 2026
(Merged from https://github.com/openssl/openssl/pull/31828)


  Commit: 59a8cf3d86324a6c774c23a7341158f02d96f6fc
      https://github.com/openssl/openssl/commit/59a8cf3d86324a6c774c23a7341158f02d96f6fc
  Author: Jakub Zelenka <[email protected]>
  Date:   2026-07-13 (Mon, 13 Jul 2026)

  Changed paths:
    M test/recipes/20-test_dgst.t

  Log Message:
  -----------
  apps: add test coverage for dgst -list

Exercise the previously uncovered show_digests() path in dgst app by
adding a subtest that runs "openssl dgst -list". It checks the header
and that sha256 and sha512 are listed, without assuming the full set of
digests which depends on the build configuration.

Assisted-by: Claude:claude-opus-4-8

Reviewed-by: Paul Dale <[email protected]>
Reviewed-by: Tomas Mraz <[email protected]>
MergeDate: Mon Jul 13 15:05:45 2026
(Merged from https://github.com/openssl/openssl/pull/31886)


Compare: https://github.com/openssl/openssl/compare/1de3ee397c92...59a8cf3d8632

To unsubscribe from these emails, change your notification settings at https://github.com/openssl/openssl/settings/notifications

-- 
You received this message because you are subscribed to the Google Groups "openssl-commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/a/openssl.org/d/msgid/openssl-commits/openssl/openssl/push/refs/heads/master/1de3ee-59a8cf%40github.com.