You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-7
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
### Developed by researchers from the Florida Institute for Cybersecurity Research (FICS Research)
4
4
5
-
The goal of secure function evaluation (SFE), sometimes referred to as secure multiparty computation (SMC), is to enable multiple parties to compute and receive the output of a function without having each party's private input exposed to any other party.
5
+
The goal of secure function evaluation (SFE), sometimes referred to as secure multiparty computation (SMC), is to enable multiple parties to compute and receive the output of a function without learning the private inputs from any other party.
6
6
7
7
We propose a hybrid two-party SFE (2P-SFE) scheme where the function is partitioned into a sequence of round functions. Some of these rounds functions are evaluated within an SGX enclave while others are evaluated using a garbled circuit.
8
8
@@ -11,7 +11,7 @@ Our protocols involve two parties: the sender (Alice) and the evaluator (Bob).
11
11
* Evaluator implementation is comprised of: State Machine + Socket + Enclave + SGX Remote Attestation + YAO (garbled circuits)
12
12
* Sender implementation is comprised of: State Machine + Socket + Enclave + YAO
13
13
14
-
#####Setup Notes
14
+
#####Setup Notes
15
15
1. Use "#if defined(\_MSC\_VER)" for Windows compilation
16
16
2. Use "#elif defined(\_\_GNUC\_\_)" for Linux gcc/make compilation
17
17
3. All code was developed for Linux
@@ -23,7 +23,7 @@ Our protocols involve two parties: the sender (Alice) and the evaluator (Bob).
23
23
9. Private key files (.pem) in enclave subdirectories were pulled from the Intel SGX SDK sample code and left for completeness
24
24
10. Run ``make`` within the sample\_libcrypto subdirectory at first to generate **libsample\_libcrypto.so**
25
25
26
-
#####Repository Contents
26
+
#####Repository Contents
27
27
Sub-directories:
28
28
29
29
***common**: code common to both evaluator's and sender's application
@@ -50,13 +50,13 @@ Top-level files:
50
50
***Makefile**
51
51
***README.md**
52
52
53
-
#####Building/Running the Code
53
+
#####Building/Running the Code
54
54
Build using the build\_runs.sh script, which will call `make`. Once built, refer to the included __HOWTO.txt__ file for invocation instructions.
55
55
56
-
#####Frigate Dependencies
56
+
#####Frigate Dependencies
57
57
We adapt Frigate (garbled circuit compiler and execution environment) for evaluation of round functions within garbled circuits. Successful compilation of the Frigate component (YAO) may be best achieved on a system with Bison version 2.7.1 and Flex version 2.5.37. Frigate is available at <https://bitbucket.org/bmood/frigaterelease>.
58
58
59
-
#####AsiaCCS'19 paper citation
59
+
#####AsiaCCS'19 paper citation
60
60
This repository contains the implementation of the hybrid protocols presented in our AsiaCCS'19 paper. The full BibTeX citation for our paper is as follows:
61
61
62
62
```
@@ -67,4 +67,4 @@ This repository contains the implementation of the hybrid protocols presented in
67
67
year = 2019}
68
68
```
69
69
70
-
Our full version, with proofs, is available on arXiv: <https://arxiv.org/abs/1905.01233>.
70
+
Our full version, with proofs, is available on arXiv: <https://arxiv.org/abs/1905.01233>.
0 commit comments