Skip to content
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

Suggest order in gNOI cert ca_certificates #22

Merged
merged 2 commits into from
Aug 29, 2019
Merged

Suggest order in gNOI cert ca_certificates #22

merged 2 commits into from
Aug 29, 2019

Conversation

samribeiro
Copy link
Member

Set expectations in the order that CA certificates should have. This helps with improving performance in the Target when building chained relationships between certificates. This is merely suggested. Certificates can still be provided out of order.

@samribeiro samribeiro requested a review from robshakir May 6, 2019 13:34
@samribeiro samribeiro self-assigned this May 6, 2019
// To improve performance in the Target, certificates can be ordered.
// Groups of chained certificates should be last, where within, the root
// certificate is the last one. E.g.:
// CertA, CertB, CertB-Root, CertC, CertC-Intermediate, CertC-Root

Choose a reason for hiding this comment

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

Sam, looks good. Please note there could also be CA-Cert for target certificate in the bundle.

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks Reshad.
Indeed, I have created another PR to cover that under the simplified security model document.

Copy link
Contributor

@robshakir robshakir left a comment

Choose a reason for hiding this comment

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

Thanks for this, this seems reasonable. LGTM.

@samribeiro samribeiro merged commit 369bb4f into master Aug 29, 2019
@samribeiro samribeiro deleted the gnoi_cert branch August 29, 2019 09:29
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