Skip to content

Commit e9859af

Browse files
authored
Merge pull request #2 from CBonnell/deltacert-validation-guidance
Add testing blub + reference to path validation
2 parents 244f0c9 + 6b67d2b commit e9859af

File tree

1 file changed

+19
-2
lines changed

1 file changed

+19
-2
lines changed

draft-bonnell-lamps-chameleon-certs.md

Lines changed: 19 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -364,6 +364,12 @@ from a Base Certificate:
364364
9. Replace the value of the signature field of the Delta Certificate
365365
template with the value of the DCD extension's signatureValue field.
366366

367+
As part of testing implementations of this specification,
368+
implementers are encouraged to verify the signature of the
369+
reconstructed Delta Certificate using the issuing Certification
370+
Authority's public key to ensure that the Delta Certificate was
371+
reconstructed correctly.
372+
367373
# Delta certificate request content and semantics {#dcr-attribute}
368374

369375
Using the two attributes that are defined below, it is possible to
@@ -498,8 +504,19 @@ using the process outlined in {{dcd-csr-create}}.
498504
# Security Considerations
499505

500506
The validation of Base Certificates and Delta Certificates follows the
501-
certification path validation algorithm defined in {{!RFC5280}}.
502-
However, there are some additional considerations for the software to
507+
certification path validation algorithm defined in {{!RFC5280}}. In
508+
particular, the certification path validation algorithm defined in
509+
{{!RFC5280}} MUST be performed prior to using a Base or Delta
510+
Certificate; it is not sufficient to reconstruct a Delta Certificate
511+
and use it for any purpose without performing certification path
512+
validation. If a use case requires it, a Delta Certificate can be
513+
reconstructed specifically for the purposes of validation to ensure that
514+
the Delta Certificate is valid for its intended purpose on final
515+
reconstruction. That being said, some form of validation such as
516+
revocation checking, and signature verification MUST always be assured
517+
at the point the certificate is used.
518+
519+
There are some additional considerations for the software to
503520
handle the Base Certificate and Delta Certificate. The Base Certificate
504521
and Delta Certificate may have different security properties such as
505522
different signing algorithms, different key types or the same key types

0 commit comments

Comments
 (0)