Skip to content

Insert suitable spec reference to RFC5280, where required#559

Open
yogeshbdeshpande wants to merge 4 commits intomainfrom
x.509-tidy-up
Open

Insert suitable spec reference to RFC5280, where required#559
yogeshbdeshpande wants to merge 4 commits intomainfrom
x.509-tidy-up

Conversation

@yogeshbdeshpande
Copy link
Copy Markdown
Collaborator

Fixes #548

Fixes #548

Signed-off-by: Yogesh Deshpande <yogesh.deshpande@arm.com>
@carl-wallace
Copy link
Copy Markdown

The change you made to section 9.2.2.1 is good but I was expecting the reference to Section 6 of RFC5280 to replace the abbreviated rules noted here: https://datatracker.ietf.org/doc/html/draft-ietf-rats-corim-10#section-9.3.4.4. Is there a reason why abbreviated certificate validation rules are sufficient in 9.3.4.4? In my review, I noted the lack of a basic constraints check as potentially problematic.

Signed-off-by: Yogesh Deshpande <yogesh.deshpande@arm.com>
@yogeshbdeshpande
Copy link
Copy Markdown
Collaborator Author

@carl-wallace , we agreed to refer it to Section 6 of RFC5280. Other types may require other validation rules, and is documented in the CoRIM Profile document by the Vendor. Changed the langauge to incorporate this..

@carl-wallace
Copy link
Copy Markdown

Thank looks better. Thanks.

Copy link
Copy Markdown
Collaborator

@nedmsmith nedmsmith left a comment

Choose a reason for hiding this comment

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

LGTM

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.

Use of X.509

4 participants