Samee Zahur

Ok, I made a few changes to make this work: ```diff $ diff -ru garble garble-modified/ diff -ru garble/gazelle.c garble-modified/gazelle.c --- garble/gazelle.c 2019-04-27 13:23:22.000000000 -0700 +++ garble-modified/gazelle.c 2019-04-27 11:36:51.730552256 -0700...

That dual execution protocol is pretty much a direct implementation of this paper: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.677.1248&rep=rep1&type=pdf. As far as I remember, yes the OT and equality checks are secure against malicious adversaries....

Did you say you were doing it on the `master` branch, or `obliv-c` branch? This repository is weird that way (sorry!). That warning can be ignored. It is caused by...

`make test` is certainly a good idea. Have the usual `CFLAGS` or some way to compile things with debug symbols or profiling instrumentation. Have a good way to do `make...

We can probably use this bug for test scripts.

Our general advice has always been that a Linux VM on Windows might be the easiest approach if you don't have a native Linux machine.

I honestly don't think I've ever seen that before. Did you get any other strange error during the build process? Do you see any changes if you run `git diff`?

Also, can you paste the output from running `uname -a` on your system? I just want to make sure this isn't related to some unusual system configuration I haven't seen...