Skip to content
This repository was archived by the owner on Jan 20, 2022. It is now read-only.

Commit 3b67e5d

Browse files
committed
fixup! [Examples] Add SQLite
Signed-off-by: Paweł Marczewski <[email protected]>
1 parent 9c5e1f1 commit 3b67e5d

File tree

3 files changed

+5
-3
lines changed

3 files changed

+5
-3
lines changed

Examples/sqlite/.gitignore

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
1-
OUTPUT
1+
/OUTPUT
22
/scripts/testdir/*
33
!/scripts/testdir/.dummy

Examples/sqlite/Makefile

-2
Original file line numberDiff line numberDiff line change
@@ -32,8 +32,6 @@ sqlite3.manifest: manifest.template
3232
-Darch_libdir=$(ARCH_LIBDIR) \
3333
$< >$@
3434

35-
# Generating the SGX-specific manifest (*.manifest.sgx), the enclave signature,
36-
# and the token for enclave initialization.
3735
sqlite3.manifest.sgx: sqlite3.manifest
3836
graphene-sgx-sign \
3937
--key $(SGX_SIGNER_KEY) \

Examples/sqlite/README.md

+4
Original file line numberDiff line numberDiff line change
@@ -48,3 +48,7 @@ That means it is safe to access the same database file from multiple processes,
4848
but only within a **single Graphene instance**. In other words, a multi-process
4949
Graphene application is OK, but multiple Graphene instances should not access
5050
the same database file concurrently.
51+
52+
Note that in a production setup, the database should be either mounted as a
53+
protected file, or from tmpfs, which would make it impossible to access from
54+
multiple Graphene instances anyway.

0 commit comments

Comments
 (0)