-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLS SubjectAltName sticky buffer/v5 #10750
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
So far, the SANs were available as a part of IssuerDN via x509_parser crate but SANs were not available to the SSLState* to be directly used to setup and match against a sticky buffer. Expose it to SSLStateConnp. Feature 5234
Add TLS SubjectAltName sticky buffer. Feature 5234
Feature 5234
Information: QA ran without warnings. Pipeline 19907 |
inashivb
requested review from
jasonish,
jufajardini and
victorjulien
as code owners
April 3, 2024 05:30
catenacyber
reviewed
Apr 3, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good Shivani
- CI : 🟢
- Code : checking now
- Commits segmentation : ok for me, even if I would squash the doc commit into the one adding the keyword
- Commit messages : ok for me,
git log | grep Feature
shows usage of either:
or#
- Git ID set : looks fine for me
- CLA : you already contributed :-)
- Doc update : Ok, maybe mention "x509 certificate"
- Redmine ticket : ok
- Rustfmt : may be done on rust/src/x509/mod.rs
- Tests : left a few questions there
- Dependencies added: none
catenacyber
reviewed
Apr 3, 2024
catenacyber
reviewed
Apr 3, 2024
catenacyber
reviewed
Apr 3, 2024
catenacyber
reviewed
Apr 3, 2024
catenacyber
reviewed
Apr 3, 2024
catenacyber
reviewed
Apr 3, 2024
catenacyber
reviewed
Apr 3, 2024
catenacyber
reviewed
Apr 3, 2024
Is this ready for #10462 ? |
Not yet. I have to incorporate the feedback that comes out of our discussions above. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Link to redmine ticket: https://redmine.openinfosecfoundation.org/issues/5234
SV_BRANCH=OISF/suricata-verify#1738
Previous PR: #10748
Changes since v4: