certz: clarify usage of CERT_SOURCE_IDEVID#261
Merged
morrowc merged 1 commit intoopenconfig:mainfrom Mar 2, 2026
Merged
Conversation
comment how CERT_SOURCE_IDEVID usage should be handled, both from the client side (clients should only set it in their leaf certificate, and should not add any explicit intermediate certs), and from the server side (servers should expand this enum to represent one or more certificates until a usable certificate chain can be formed). This gives the client a defined workflow to keep it vendor-neutral, but means that if the device would require an intermediate cert to make the ssl profile usable, then the server has the freedom to append it.
morrowc
approved these changes
Mar 2, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
comment how CERT_SOURCE_IDEVID usage should be
handled, both from the client side (clients should
only set it in their leaf certificate, and should
not add any explicit intermediate certs), and from
the server side (servers should expand this enum
to represent one or more certificates until a usable
certificate chain can be formed).
This gives the client a defined workflow to keep it
vendor-neutral, but means that if the device would
require an intermediate cert to make the ssl profile usable,
then the server has the freedom to add it.