Skip to content

Commit 397d05c

Browse files
briannevillemorrowc
authored andcommitted
certz: clarify usage of CERT_SOURCE_IDEVID
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.
1 parent e89bb23 commit 397d05c

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

certz/certz.proto

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -487,6 +487,14 @@ message Certificate {
487487

488488
// certificates present on the device already
489489
CERT_SOURCE_OIDEVID = 1;
490+
491+
// CERT_SOURCE_IDEVID can only be used on the leaf Certificate in a
492+
// CertificateChain, and that if the leaf Certificate has cert_source
493+
// set to CERT_SOURCE_IDEVID, then no Parent CertificateChain
494+
// should be set.
495+
// Internally, the handling for CERT_SOURCE_IDEVID may involve the device
496+
// configuring one or more certificates in the ssl profile, so that it
497+
// forms a valid and usable certificate chain.
490498
CERT_SOURCE_IDEVID = 2;
491499
// self-signed certificate generated on device
492500
CERT_SOURCE_SELFSIGNED = 3;

0 commit comments

Comments
 (0)