FS and PCS considerations#45
Open
xisentian wants to merge 2 commits into
Open
Conversation
Collaborator
|
This looks good to me. I'm not an expert on details of what FS and PCS imply, but at least the motivations are definitely correct. |
Owner
|
I suggest @xisentian do the following: separate FS and PCS, as they have very different security properties and requirements. |
Contributor
Author
FS and PCS are security properties that should go hand-in-hand to minimize the fallouts of a key compromise. If we separate them as requirements, we would be inviting architectures that have one but not the other (e.g. FS only) which I don't believe should be the case. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
As discussed during IETF-123