Add documentation on Moose - introduction and protocol implementation guide #1038
Conversation
|
|
||
|
|
||
| ### Threat model at Cape: honest, but curious | ||
| It is permissible that if parties collude with each other, they can use result values to reconstruct inputs |
There was a problem hiding this comment.
Not sure I understand this. It's (2,3) secret sharing, meaning that if any two parties collaborate they can reconstruct the secret.
|
|
||
| ### Threat model at Cape: honest, but curious | ||
| It is permissible that if parties collude with each other, they can use result values to reconstruct inputs | ||
| This threat model is less strict than active security, which takes into account that perhaps not every party follows given protocols |
There was a problem hiding this comment.
I believe that there's no need to mention about active security here if we don't use it.
|
|
||
|
|
||
| ### How to implement new protocols in Moose | ||
| Example: How to implement an operation edsl.ones(), which creates a vector of ones with a given lenght |
| ### How to implement new protocols in Moose | ||
| Example: How to implement an operation edsl.ones(), which creates a vector of ones with a given lenght | ||
|
|
||
| Summary |
There was a problem hiding this comment.
Perhaps we should also specify why we need to do these changes, for each subsection?
|
hey @ekloberdanz, mind giving this PR a slightly more informative title (and without the prefix)? |
ekloberdanz
changed the title
For sure! I did not notice that the PR title was just set to whatever the branch name was. |
documentation/Introduction.md
Outdated
| - Elk compiler | ||
| - Moose runtime | ||
|
|
||
| ### Cape's usage of Moose/PyMoose |
There was a problem hiding this comment.
Perhaps this subsection is just confusing more than helping (for OSS)
add a guide on how to implement a new protocol add spacing add indent fix indent update documentation
ekloberdanz
force-pushed
the
ellie/add-documentation
branch
from
0108f2e
to
258e052
Compare
This PR adds notes on Moose and implementing protocols in Moose that may be useful to future contributors. It is not complete/finished, just a first step. Note, there is some overlap with the Moose readme. This PR just captures my notes that I thought would be useful to others.