You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.The text was updated successfully, but these errors were encountered: