Separate anchor validation functionality from certificate operations
Registered by
Doug Chivers
Currently the anchor certificate operations and validation process both exist in the anchor package. To enable the re-use of the validators in other software, they should be split into a separate packet, such as anchor.validators. The validate_csr functionality from certificate operations should be moved into this new package and modified to return a list of tuples, with the name of the validator and its pass/fail status, rather than aborting if a single validator fails.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Doug Chivers
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)