Apache Pirk (Incubating)

Clone this repo:
  1. 5ebe1bf [PIRK-41]: Add JSON Serialization for Java Objects -- closes apache/incubator-pirk#42 by smarthi · 1 year, 2 months ago master
  2. 697913a pushing hotfix for bug in SystemConfiguration local properties dir parsing by eawilliams · 1 year, 2 months ago
  3. 0912bb6 [PIRK-37]: Rename package for test classes to be org.apache.pirk.* -- closes apache/incubator-pirk#39 by smarthi · 1 year, 2 months ago
  4. 9d7b46d [PIRK-36]: Ensure Schema Properties and Registries are Reset at the Beginning of Relevant Tests -- closes apache/incubator-pirk#38 by eawilliams · 1 year, 2 months ago
  5. 0237de6 [PIRK-35]: Execute tests in Parallel -- closes apache/incubator-pirk#37 by smarthi · 1 year, 2 months ago

Apache Pirk (incubating) is a framework for scalable Private Information Retrieval (PIR). The goal of Pirk is to provide a landing place for robust, scalable, and practical implementations of PIR algorithms.

Documentation

Please see the Apache Pirk website for documentation.

Getting Started

Pirk is written in Java and currently uses a Maven build system with a single level pom.xml. As such, Pirk may be built via ‘mvn package’.

For convenience, the following POM files are included:

  • pom.xml — Pirk pom file for Hadoop/YARN and Spark platforms
  • pom-with-benchmarks.xml — Pirk pom file for running Paillier benchmarking testing

Pirk may be built with a specific pom file via ‘mvn package -f ’

Dependencies can be found in the pom.xml file and include Apache Hadoop, Apache Spark, and Elasticsearch. Currently, Pirk may be utilized in a distributed Hadoop/MapReduce or Spark framework as well as in standalone mode.

If you are a User, please check out the For Users section of the Pirk website.

If you are a Developer, please check out the For Developers section of the Pirk website.

Pirk Basics

Private Information Retrieval (PIR) enables a user/entity to privately and securely obtain information from a dataset, to which they have been granted access, without revealing, to the dataset owner or to an observer, any information regarding the questions asked or the results obtained. Employing homomorphic encryption techniques, PIR enables datasets to remain resident in their native locations while giving the ability to query the datasets with sensitive terms.

There are two parties in a PIR transaction - the Querier, the party asking encrypted questions, and the Responder, the party holding the target data and answering encrypted questions (performing encrypted queries).

Pirk is centered around the Querier and the Responder.

In Pirk, the Querier is responsible for the following:

  • Generating the encrypted query vectors (representing encrypted questions)
  • Generating the necessary decryption items for each query vector
  • Decrypting encrypted query results obtained from the Responder

Once the Querier generates an encrypted query, it must be sent to the Responder.

In Pirk, the Responder is responsible for the following:

  • Performing encrypted queries over their target datasets (using encrypted query vectors)
  • Forming the encrypted query results

The encrypted query results must be sent from the Responder back to the Querier for decryption.

Pirk employs generic data and query schemas, specified via XML files, that are shared between the Querier and Responder to enable flexible and varied data and query types.

License

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

    (http://www.apache.org/licenses/LICENSE-2.0)
    
    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License. See accompanying LICENSE file.

Apache Software Foundation Incubation

Apache Pirk is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the name of Apache TLP sponsor. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.