Add X.509 trust model guidance #240
Open
Conversation
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
andyparsons
suggested changes
Sep 17, 2025
chalford
requested changes
Sep 17, 2025
chalford
requested changes
Oct 7, 2025
|
|
||
| The *CAWG trust list* MUST be configured to recognize certificates with `id-kp-emailProtection` (1.3.6.1.5.5.7.3.4) for *identity assertions* issued during the validity window described above. | ||
|
|
||
| For this EKU, the following certificate policy IDs MUST be accepted: |
There was a problem hiding this comment.
Is this intended to say "only certificates with these CPs will be accepted"? If so:
- The wording should be adjusted
- Does this reflect real-world usage? It's a bit of a wild west out there in terms of the CPs being added to certificates.
lrosenthol
requested changes
Oct 9, 2025
Co-authored-by: Leonard Rosenthol <leonardr@lazerware.com>
chalford
reviewed
Oct 9, 2025
Co-authored-by: Charlie Halford <charlie.halford@gmail.com>
# Conflicts: # docs/modules/ROOT/partials/credential-types/x509.adoc
chalford
requested changes
Oct 17, 2025
chalford
reviewed
Oct 21, 2025
| IMPORTANT: This list does not include Mailbox-validated or “legacy” certificate purpose OIDs. | ||
| + | ||
| NOTE: The issuance criteria for such certificates are specified by the CA/Browser Forum in https://cabforum.org/uploads/CA-Browser-Forum-SMIMEBR-1.0.11.pdf[Baseline Requirements for the Issuance and Management of Publicly‐Trusted S/MIME Certificates, version 1.0.11] and may be updated in subsequent versions. | ||
| 4. The certificate chains up to one of the following roots of trust: |
There was a problem hiding this comment.
Suggested change
| 4. The certificate chains up to one of the following roots of trust: | |
| 4. The lists below may include both CA and end-entity certificates. The certificate under validation MUST either be directly included in one of these lists, or have a valid chain of trust to a certificate present in one of these lists. |
The IPTC list currently includes end-entity certificates, can we ensure validators support this? That's usually the assumption with end-entity certs in trust lists, but it would be good to be explicit.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 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.
No description provided.