Skip to content

Decode OCSP Revocation Reason#7241

Merged
dgarske merged 1 commit intowolfSSL:masterfrom
ejohnstown:ocsp-revoke-reason
Feb 12, 2024
Merged

Decode OCSP Revocation Reason#7241
dgarske merged 1 commit intowolfSSL:masterfrom
ejohnstown:ocsp-revoke-reason

Conversation

@ejohnstown
Copy link
Copy Markdown
Contributor

Description

The ASN.1 parser wasn't handling the OCSP response correctly when there was a revocation reason included in the response. The encoded reason value is constructed, and was getting marked as not constructed in the parser. Changed the flag to mark it as constructed.
(Fixes ZD 17027)

Testing

I have a set of certificates I've been using for some testing. I added one for a server and use it with an OCSP lookup. I have two alternate certificate lists where this certificate is revoked: one without a revocation reason and one with the optional reason. Both should report the certificate as revoked. (The original report was that the lookup failed.)

Checklist

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

1. The ASN.1 parser wasn't handling the OCSP response correctly when
   there was a revocation reason included in the response. The encoded
   reason value is constructed, and was getting marked as not
   constructed in the parser. Changed the flag to mark it as
   constructed.
@ejohnstown
Copy link
Copy Markdown
Contributor Author

retest this please

Copy link
Copy Markdown
Member

@dgarske dgarske left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would really like a test case that covers this but I understand that is difficult

@dgarske dgarske merged commit 2ebc897 into wolfSSL:master Feb 12, 2024
@ejohnstown ejohnstown deleted the ocsp-revoke-reason branch February 12, 2024 23:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants