-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Remove non-working check from x509_get_subject_alt_name #2855
Remove non-working check from x509_get_subject_alt_name #2855
Conversation
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.
Thanks for the fix! Looks good.
@@ -662,7 +658,7 @@ static int x509_get_subject_alt_name( unsigned char **p, | |||
} | |||
|
|||
/* | |||
* Check that the SAN are structured correct. |
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.
This change is outside of the PRs scope. I'd suggest not mixing in extra changes with the main ones. But this is far from being a blocker.
The state is |
This is a minor improvement that doesn't require backporting. It does require a changelog. Can you please rebase this PR on top of
|
b94f9c6
a9783de
to
f8c6ea6
Compare
FIx one comment. Signed-off-by: irwir <[email protected]>
Signed-off-by: irwir <[email protected]>
Thanks. |
Hi @irwir . Sorry this PR stalled. Unfortunately you're change log entry filename conflicts with another one. Can you use a name that uniquely identifies this PR? Thanks. |
Signed-off-by: irwir <[email protected]>
Altered the file name. |
Thanks.
The entries are only collated at release time so they must all be unique between releases. I accept the guidance needs improvement. |
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.
LGTM
Description
That fixes #2802
The changed comment might also be changed by @hanno-arm in his PR.
Status
READY
Requires Backporting
NO
Which branch?
Development
Migrations
NO