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

Add Java DaCapo benchmark sample provide fixes #646

Open
wants to merge 22 commits into
base: oe_port
Choose a base branch
from
Open

Add Java DaCapo benchmark sample provide fixes #646

Changes from 1 commit
Commits
Show all changes
22 commits
Select commit Hold shift click to select a range
28ece2d
Fix dependency in Makefile for Java sample
prp Jul 19, 2020
2c6ee45
Output thread struct address in backtraces
prp Jul 19, 2020
adb6119
Move dumping of mount table to correct location
prp Jul 19, 2020
1d3b408
Add Java DaCapo benchmark sample
prp Jul 19, 2020
6b4ce95
Run first DaCapo benchmark by default
prp Jul 19, 2020
f5f5d04
Debugging DaCapo benchmark h2
prp Jul 19, 2020
7368de3
Fix bug to correctly report segfault address in signal handler
prp Jul 22, 2020
d5d745e
Improve mmap logging
prp Jul 22, 2020
fbaa03c
Pass through SGXLKL_TRACE_SIGNAL correctly
prp Jul 22, 2020
18d3f1c
Update Java DaCapo benchmark sample
prp Jul 22, 2020
dbb7ed9
Add Java DaCapo benchmark test to CI to check correct signal handling
prp Jul 22, 2020
30d52f4
Fix spurious line in Makefile
prp Jul 23, 2020
30a553e
Revert OE changes
prp Jul 27, 2020
c6af984
Document limitations of in-enclave signal handling
prp Jul 27, 2020
7518776
Add enclave_config option "unsafe_host_signals"
prp Jul 27, 2020
a65be49
Update signal handling to return dummy fault address in hw mode
prp Jul 27, 2020
09b5a1f
Update Java DaCapo benchmark sample
prp Jul 27, 2020
1c9e089
Update Java DaCapo test
prp Jul 27, 2020
9dd5458
Point to previous OE branch
prp Jul 27, 2020
fdb1381
Set default for unsafe_host_signals to true
prp Jul 27, 2020
4a2993a
Update enclave config ref file in test
prp Jul 27, 2020
066e154
Address review comments
prp Jul 27, 2020
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
Document limitations of in-enclave signal handling
  • Loading branch information
@prp
prp committed Jul 27, 2020
commit c6af984a4c20b9db9c4ba70e5fb9147042dc0d9b
6 changes: 6 additions & 0 deletions docs/Incompatibilities.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,6 110,12 @@ All of the Linux clocks are driven from the monotonic counter, so anything depen
Additionally, the time exposed in the enclave is untrusted.
The enclave may communicate with an external trusted time source but that can give only a lower bound on the current time: a malicious host could cause the enclave to sleep for an unbounded amount of time.

### Limited signal handling

With SGX1, signals such as `SIGSEGV` must be reported by the untrusted host and cannot be independently validated by the enclave.
In addition, the address that resulted in a page fault cannot be obtained at all, and an application signal handler inside the enclave therefore always reports the faulting address as 0x0.
(The enclave configuration setting `unsafe_host_signals` can be used to control if SGX-LKL exposes untrusted signals from the host to the enclave.)

Summary of security implications
--------------------------------

Expand Down