Security problems of _B2A_private() function

Question

dujifeng opened this issue 3 years ago · comments

The _B2A_private function seems unsafe. a0, a1, a2 is known to all parties, which is unsafe. a0, a1, a2 is for masking, but konwn to all parties.
neg_x1_neg_x2[0][1] = neg_x1_neg_x2[1][0] should be forbidden? i thought you just can't simply put device[0]'s number to device[1] without any other operation.
Can you teach me how to implement the process just as the way described in ABY3 paper?

Zhicong Huang (Zico) · Answer 1 · Mon Oct 25 2021 18:12:11 GMT+0800 (China Standard Time)

As pointed out in our email communication, these features come inherent with Tensorflow and has NO security problem.
I will close this issue.

Zhicong Huang (Zico) · Answer 2 · Mon Oct 25 2021 18:14:18 GMT+0800 (China Standard Time)

@dujifeng could you please close this issue? Just realize that I don't have permission to do so :).

dujifeng · Answer 3 · Mon Nov 22 2021 10:14:08 GMT+0800 (China Standard Time)

I'm sorry, I just saw it...Thank you for your answer!