Skip to content
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

output MAC check? #6

Open
weikengchen opened this issue Apr 13, 2020 · 3 comments
Open

output MAC check? #6

weikengchen opened this issue Apr 13, 2020 · 3 comments
Labels

Comments

@weikengchen
Copy link
Contributor

weikengchen commented Apr 13, 2020

It seems that the implementation does not check the MAC of the outputs (even with __debug turned on). I feel that it is okay for benchmark purposes since the overhead is comparably small.

But, should the code for output MAC check be added (which would be invoking check_MAC)? Or should we leave as it is?

My local test, which tampers party 2's value before https://github.com/emp-toolkit/emp-agmpc/blob/master/emp-agmpc/mpc.h#L416, suggests that one malicious party can, however, tamper with the output since the party 1 does not check the MAC.

@wangxiao1254
Copy link
Member

Thanks. It should be fixed. Will find time to fix it soon :)

@wangxiao1254
Copy link
Member

Debug mode is not secure, only for development. Functions called in the debug mode will send out Delta!

@weikengchen
Copy link
Contributor Author

Thanks. That is important information (I have been assuming that debug mode turns on the MAC checks and makes it maliciously secure).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants