Implement master token-protected entity authentication scheme. #43
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
…AuthenticationData$parse() to use a callback for asynchronous processing.
…icationFactory.createData() asynchronous.
This scheme can be used to authenticate as a different entity without exposing the new entity authentication data to third-party observers by using an existing master token and its session keys. Application data encryption and integrity cannot be promised because the message must be protected using the encapsulated entity authentication scheme (otherwise no authentication actually occurs) which has unknown crypto properties.
wmiaw
added a commit
that referenced
this pull request
Aug 26, 2015
Implement master token-protected entity authentication scheme.
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.
Resolves #18.
This scheme can be used to authenticate as a different entity without exposing the new entity authentication data to third-party observers by using an existing master token and its session keys.
Application data encryption and integrity cannot be promised because the message must be protected using the encapsulated entity authentication scheme (otherwise no authentication actually occurs) which has unknown crypto properties.