A fork of SealPIR (v2.1) with patches for PIROS microbenchmarking

Kim Laine 603ab7e074 Fix typo in README.md 6 jaren geleden
.gitignore fbd6c9bd26 Initial commit 6 jaren geleden
CMakeLists.txt dead23d39d Updated to SEAL 2.3.1 6 jaren geleden
LICENSE 76e1a93d3c Initial commit 6 jaren geleden
README.md 603ab7e074 Fix typo in README.md 6 jaren geleden
main.cpp dd7ffc3e4a SealPIR v0.1 6 jaren geleden
pir.cpp dead23d39d Updated to SEAL 2.3.1 6 jaren geleden
pir.hpp dd7ffc3e4a SealPIR v0.1 6 jaren geleden
pir_client.cpp dead23d39d Updated to SEAL 2.3.1 6 jaren geleden
pir_client.hpp dd7ffc3e4a SealPIR v0.1 6 jaren geleden
pir_server.cpp dead23d39d Updated to SEAL 2.3.1 6 jaren geleden
pir_server.hpp dd7ffc3e4a SealPIR v0.1 6 jaren geleden

README.md

SealPIR: A computational PIR library that achieves low communication costs and high performance.

SealPIR is a (research) library and should not be used in production systems. SealPIR allows a client to download an element from a database stored by a server without revealing which element was downloaded. SealPIR was introduced in our paper.

Compiling SEAL

SealPIR depends on SEAL 2.3.1 (link). Download SEAL, and follow the instructions in INSTALL.txt to install it system-wide.

Compiling SealPIR

Once SEAL 2.3.1 is installed, to build SealPIR simply run:

cmake .
make

This should produce a binary file bin/sealpir.

Using SealPIR

Take a look at the example in main.cpp for how to use SealPIR.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.