Weikeng Chen

If we don't just sign the LSB, but sign the hashes of two labels (the 0-label and 1-label), there is still an obstacle: Maybe a bit flip only makes a...

The overkill solution is to sign everything, including OT and the circuit. So, I smell some academic research here... even in the malicious case, we don't want a network attacker...

The motivating example for malicious case (off-topic for Obliv-C): 10 companies are actually honest, but they run a maliciously secure 10-party federated learning platform. After THREE months of computation, they...

I have previously played with Obliv-C on MacOS. There are just too many differences between Linux and MacOS in many aspects. Therefore, I would strongly recommend you to use Linux...

This is a more general question that I would refer you to other online resource: https://linoxide.com/how-tos/linux-make-command-examples/ (this link is better) So, at a high level, at the end of the...

Nope. Obliv-C relies on CIL, which can basically support many features in C, but no guarantee in C++. https://people.eecs.berkeley.edu/~necula/cil/

I think in this case, space needs to be initialized via `malloc` instead of `obliv int arr[150][150]`.

It looks like OblivC has some implementations on the dual-execution protocol: https://github.com/samee/obliv-c/blob/obliv-c/src/ext/oblivc/dualex.c#L133 But I haven't used it, and right now, there is a limitation: ``` fprintf(stderr,"Right now, Dualex protocol requires...

I think your question is about whether the oblivious transfer is done maliciously secure, in order to enable dual execution to be secure. I would leave this question to @samee....

While, not in the Bay Area Google, but Google Switzerland.