https://github.com/SOF3/enclavlow

A Java flow analysis tool for SGX data sensitivity. This is my final year project.
https://github.com/SOF3/enclavlow

flow-analysis sgx-data-sensitivity

Last synced: 1 day ago
JSON representation

A Java flow analysis tool for SGX data sensitivity. This is my final year project.

• Host: GitHub
• URL: https://github.com/SOF3/enclavlow
• Owner: SOF3
• Created: 2020-10-17T15:41:47.000Z (over 3 years ago)
• Default Branch: master
• Last Pushed: 2021-05-23T05:54:50.000Z (about 3 years ago)
• Last Synced: 2024-02-29T03:33:06.257Z (4 months ago)
• Topics: flow-analysis, sgx-data-sensitivity
• Language: Kotlin
• Homepage:
• Size: 5.74 MB
• Stars: 5
• Watchers: 4
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Lists

• Awesome-SGX-Open-Source - https://github.com/SOF3/enclavlow

README

        
# enclavlow

A Java flow analysis tool for SGX data sensitivity

## Modules

- `util`: Internal non-enclavlow-specific utilities

- `core`: Core module for flow analysis

- `plugin`: Gradle integration plugin

- `api`: API to include from user code

- `doc-fig`: Module for generating image assets used in docs

![](build/reports/dependency-graph/dependency-graph.png)

## API

### `enclavlow-core`

The `analyzeMethod` function returns a Contract Flow Graph (CFG) for a single method.

The CFG detects whether the method is an ECall/OCall,

and presents the information flow throughout the method.

## Tests

To run the test cases in the `enclavlow-core` module, use the gradle task:

```

./gradlew core:test

```

This command requires the graphviz `dot` command to be in PATH.

For the sake of convenience, all test case classes are compiled together with the test runtime,

and the test runtime classpath is used as the classpath for soot.

The test case classes are located in `core/src/test/java`,

and the test case results are checked in `core/src/test/kotlin`.

The JUnit test results can be found in `core/build/reports/test/test/index.html`.

For each `testMethod` test case,

the final Local Flow Graphs that contribute to output contract graph

are rendered by `dot` in the `core/build/lfgOutput` directory (see `index.html`).

(Due to use of parallel tests, the order in `index.html` is highly inconsistent)