Added 'CT' Assertion for SCION End Entity PKI #226
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As part of the implementation effort for the End Entity PKI, a new assertion with "CTProof" type was created. The assertion will contain absence or presence proofs for a certain ISD.
The information on the type (absence/presence) of the proof and the particular ISD it is relevant to will be encoded in the subject, in the format:
_[ISD_NAME]._[ABS|PRE].example.comThe verification of a presence proof is to be carried out by the client - it will be integrated in rdig when the proofs reach a stable binary format.
This change is