We are a little confused by the usage of leaky delta OT to generate TinyOT AND triples in the repo.
According to the original paper, the security proof is based on the assumption of a maliciously secure aBit:
https://eprint.iacr.org/2017/030
In the implementation section, you mentioned about using the following paper's approach, which gives a construction from leaky delta OT to non-leaky delta OT:
https://eprint.iacr.org/2016/1069.pdf
But we couldn't find such a construction in the code. The code turns out to directly to use leaky delta OT to construct TinyOT AND triples.
Could you explain this in more detail? Is there a missing reference for the implementation?
Hi,
We are a little confused by the usage of leaky delta OT to generate TinyOT AND triples in the repo.
According to the original paper, the security proof is based on the assumption of a maliciously secure aBit: https://eprint.iacr.org/2017/030
In the implementation section, you mentioned about using the following paper's approach, which gives a construction from leaky delta OT to non-leaky delta OT: https://eprint.iacr.org/2016/1069.pdf
But we couldn't find such a construction in the code. The code turns out to directly to use leaky delta OT to construct TinyOT AND triples.
Could you explain this in more detail? Is there a missing reference for the implementation?