https://github.com/plsyssec/fact-eval
https://github.com/plsyssec/fact-eval
Last synced: 4 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/plsyssec/fact-eval
- Owner: PLSysSec
- Created: 2018-05-02T01:40:14.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2019-03-28T22:51:43.000Z (about 7 years ago)
- Last Synced: 2025-07-29T11:55:35.516Z (11 months ago)
- Language: C
- Size: 19.8 MB
- Stars: 0
- Watchers: 8
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# FaCT Case Studies
This repository contains the ported code for the case studies in the FaCT paper,
as well copies of each cryptographic library for the purposes of
benchmarking. The directory already contains pre-built object files and
assembly files for each case study, built for a 64-bit Ubuntu environment. If
you would like to rebuild the files yourself, you can follow the instructions
below to rebuild them from the [FaCT source files](https://github.com/PLSysSec/FaCT).
#### Comparison of FaCT and C implementations
Refer to the table in [comparison.md](/comparison.md).
#### Virtual machine image
You can download a [VM image pre-configured for building the FaCT compiler and case studies](https://drive.google.com/open?id=1xzw4Ohsdj4WqxJPl1RvvxSnhysMSejPi).
The file `fact.ova` should have a SHA256 sum of `089398c85c5074d911c2f2b67ca22df453235e8733f1eb283c71717cf70f714c`.
#### (Re)compiling FaCT ports
To rebuild the FaCT implementations, first configure your environment:
`export FACTC="/path/to/factc"` . Then, from the `fact-eval`
directory, run `make generate` . This will recompile the FaCT source files
for each case study.
#### Compiling case studies
To compile the case studies, you will need `autoconf`:
```sudo apt-get install autoconf libtool-bin```
Then, to compile all of the case studies, run `make compile` from the `fact-eval` directory.
#### Running benchmarks and code count
To run code count, you will need `cloc`:
```sudo apt-get install cloc```
`make bench loc ; cat results.txt ; cat clocs.txt`
To run the benchmarks, run `make bench` from the `fact-eval` directory. This
will run each case study's respective benchmarking suites and collect the
results into a file called `results.txt`.
To run code count, run `make loc` from the `fact-eval` directory. This will run
a code count on each case study's FaCT code and corresponding C implementation,
using `cloc --force-lang=c++`. The results are collected into `clocs.txt`.
Note: We force `cloc`'s language parser to C++ for all files (even C
implementations) to correctly handle C++-style comments.
#### Validating constant-time
To evaluate the case studies using dudect, you must first build the dudect test
frameworks for each case study:
```
cd dudect/
make all
```
The evaluation procedure simply consists of allowing each binary to run for a
suitably large number of sample sizes, and checking that the output continues
to report: "For the moment, maybe constant time." The provided helper script,
`run-all-10m.sh`, will run each test framework for 10 minutes while capturing
output, as a convenience.
#### Acknowledgements
We thank the anonymous PLDI and PLDI AEC reviewers for their suggestions and
insightful comments.