Maliciously secure bit authentication / Refactoring #78
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
- Simplifying AuthBit - Batched bit authentication API - KOS15 base OT - KOS15 stub
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This includes a number of changes, large and small:
AuthBit, since we don't actually need bit IDs and can base everything on indices into arrays of a known lengthPartyto make it a communication harness only, so everything else can be tested more easily in isolationrun_mpcexampleUnfortunately, the base OT we already have since #48 was fixed is not sufficient for secure use in an OT extension, since it cannot achieve UC-security. Therefore I'm implementing the base OT from CSW20 which was specifically designed to be secure and efficient for use in KOS15.