-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Security model? #185
Comments
Hello, Everything has to be semi honest so far. If the server is used as a crypto provider (e.g. to generate beaver triplets), then the server cannot collude with any subset of compute parties. This is the default behavior on the master branch. The branch merge-preprocessing changes the default behavior to use preprocessing protocols to generate crypto material. In that case, the server can collude with any subset of compute parties. The compute parties themselves have two scenarios:
Finally, Input parties that do not participate in the computation can collude with any subset of each others and other parties. Note that in JIFF computation parties can be 2, 3, or more. There is no upper limit. |
Thank you @KinanBab ! |
Thank you so much for JIFF!
I have a question on the security model. As far as I know, there are 3 roles in JIFF: 1 server, 2 or 3 computation parties, N input parties. Which ones can be semi-honest or malicious? Which ones must be non-colluding? I didn't find such information in jsdoc nor in your presentations.
Thanks in advance!
The text was updated successfully, but these errors were encountered: