Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update ORTOA-TEE Readme #116

Merged
merged 6 commits into from
Dec 29, 2023
Merged

Update ORTOA-TEE Readme #116

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
c78d08f
Update ortoa-tee readme
jasondu7297 Dec 29, 2023
8eb4736
upload diagram
adriandavila Dec 29, 2023
e354cda
bigger diagram
adriandavila Dec 29, 2023
7810447
add svg diagram
adriandavila Dec 29, 2023
18e3a5f
Remove svg and update readme
jasondu7297 Dec 29, 2023
1f55c3e
Link install and build in readme
jasondu7297 Dec 29, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Remove svg and update readme
  • Loading branch information
@jasondu7297
jasondu7297 committed Dec 29, 2023
commit 18e3a5fd25d55c3e458ae664888fa171f9f2b541
13 changes: 8 additions & 5 deletions ortoa-tee/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# ORTOA-TEE

ORTOA - a One Round Trip Oblivious Access protocol that reads or writes data stored on remote storage *in one round without revealing the type of access*.
ORTOA - a family of One Round Trip Oblivious Access protocols that reads or writes data stored on remote storage *in one round without revealing the type of access*.

The ORTOA-TEE project implements this access protocol leveraging the cryptographic guarantees of trusted execution environments (hardware enclaves) and benchmarks the performance.

Expand All @@ -13,7 +13,10 @@ If a cloud vendor can provide hardware enclaves (i.e., TEEs), an application can

## Design & Implementation
The ORTOA-TEE data flow is as follows:
1. Client sends a request to an untrusted host with the following packet

<img src="docs/ortoa-tee-diagram.png" width="600">

1. Client sends a request to an untrusted host with the following packet:
1. Operation type *C* (GET or PUT)
2. Key *k* (an unencrypted integer)
3. Value *v<sub>new</sub>* (an encrypted string) (for GET requests, the value is randomly generated to maintain uniformity between operation types)
Expand All @@ -22,9 +25,9 @@ The ORTOA-TEE data flow is as follows:
4. The enclave conducts a decryption and encryption based on the following rules:
- If operation *C* is GET: decrypt and re-encrypt *v<sub>old</sub>*
- If operation *C* is PUT: decrypt and re-encrypt *v<sub>new</sub>*
5. Return the encrypted value, *v<sub>enclave</sub>*, to untrusted host
6. Untrusted host puts the value, *v<sub>enclave</sub>* into database with key *k*
7. Untrusted host returns the value, *v<sub>enclave</sub>* to client
5. Return the encrypted value *v<sub>enclave</sub>* to untrusted host
6. Untrusted host puts the value *v<sub>enclave</sub>* into database with key *k*
7. Untrusted host returns the value *v<sub>enclave</sub>* to client

## Scripts & Utilities

Expand Down
Loading