Implement ICA2 as a special case of a subCA of ICA1 #161
Labels
No labels
Compat/Breaking
Difficulty/Architectural
Difficulty/Easy
Difficulty/Hard
Help Wanted
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Security
Silenced Alert
Status/Abandoned
Status/Blocked
Status/Need More Info
Status/Postponed
Tracking Issue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: afnix/infra#161
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ICA2 has nothing special in this infrastructure, it should be a subCA property of ICA1, unlocking parallel paths for ICA2 for future intermediate CA rotations.
Once this is done, ICA1 should become a property of subCA of the offline root CA, enabling parallel paths for offline ICA1s for future intermediate CA rotations.
Once this is done, the root & intermediate CA components should support cross-signature enabling parallel paths for the root CA itself for future root CA rotations.