-
Notifications
You must be signed in to change notification settings - Fork 57
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
is using a TCCR hash with random OT KOS safe? #25
Comments
Hi @themighty1. The person familiar with this code is currently out, but they'll get back to you once they return. |
The paper that the current TCCR implementation is based on is: https://eprint.iacr.org/2019/074.pdf. See: https://github.com/GaloisInc/swanky/blob/master/scuttlebutt/src/hash_aes.rs#L52 There's been some research since that suggests that a TCCR with tighter concrete security is necessary, see: https://eprint.iacr.org/2019/1168.pdf. Does that help? |
Hi, thank you for the response and the link. Sry, I did not originally specify that I had random OT KOS in mind. Indeed, the But in ocelot, a Line 156 in bf632db
I was trying to better understand if maybe I was misunderstanding something or there was some other work I missed. I would appreciate you sharing your thoughts on this, @Isweet . |
Looking through the implementation (in When you say:
Are you referring to Table 2 or somewhere else in the paper where they make that explicit? I may have missed that. |
Thanks for pointing that out. |
FYI, here's Lance's and my take on this question osu-crypto/libOTe#116 |
Hi, ocelot currently uses a TCCR hash for breaking correlations after the KOS check acc.to this line
swanky/ocelot/src/ot/kos.rs
Line 106 in bf632db
However, the security proof of the KOS paper uses a random oracle.
Since we are also implemting a KOS OT extension, we're trying to understand has there been any recent work which proves KOS security with a TCCR hash? Or is this a liberty that ocelot is taking without relying on a formal proof?
Thanks.
The text was updated successfully, but these errors were encountered: