Jack Doerner

[Suggestion] Merging Multiple Displays

2

About a year ago I forked this project to create a quick-and-dirty modified version which merges two displays into one rather than splitting one into two. Recently I noticed this...

Improvements to protocol splitting

3

Instead of generating new OT extensions, all yao protocols share a single extension box, and use GCC atomics to distribute nonces among themselves without collisions. This saves quite a bit...

I noticed a while back that, although correlated OT code exists, YGC doesn't actually use it (nor does anything else). I have a candidate implementation [here](https://github.com/jackdoerner/obliv-c/commit/5425cc7d803f54666976b11183688eceab02070d) (note that it's a...

Thread splitting is expensive due to OT extension setup time

4

Under the current codebase, if you split the YGC protocol, you have to wait something like 300ms for OT extensions to be set up, which is a very long time,...

If one writes an `obliv` function, and then writes a forward declaration of that function that lacks the `obliv` qualifier in a header that is `#include`d, it seems that obliv-c...