Samee Zahur

Sorry, I should have better error handling. revealObliv functions convert from an obliv value to a regular one. So you want to reveal z, not x.

Ohh ... this is in main(). Yes, reveal only works inside a protocol, which needs to be started using execYaoProtocol()

If you enter values through feedObliv, the only way you can retrieve them is through reveals. However, directly assigning obliv int x = 5 won't keep x secret, since both...

Actually, there is a way. Obliv-C, as an optimization, does constant propagation. So if you hardcode values or assign them directly without using `feedObliv`, even `obliv` types will carry plaintext...

My bad. Try `&result`. I think the function takes a pointer.

I think what we need is some kind of a wiki site. If you set one up, I will gladly link to it from my readme.

Not really. You can use anything that suits you. I'd suggest going for something simple, but has the ability to export contents in some standard format that is widely accepted...

Thanks a lot. Since you seem to have the system already up and running, can you print out some of the error messages that led you to the fixes? That...

@jackdoerner

Ah, no actually. This is an example of a micro-optimization that helped, but made the code harder to read. Yes, it is filling up the buffer with two copies of...