Even if the engine could live with 2.7.0, the latest libpEpTransport needs 2.7.1. Let us use it. Also add libpEpTransport as a dependency, even if the automatic gitlab build system does not support it yet.
|10 months ago|
|.gitlab-ci-files||1 year ago|
|api||1 year ago|
|asn.1||10 months ago|
|build-android||2 years ago|
|build-mac||12 months ago|
|build-windows||1 year ago|
|codegen||11 months ago|
|db||11 months ago|
|doc||12 months ago|
|pEpMIME||1 year ago|
|scripts||11 months ago|
|src||10 months ago|
|test||10 months ago|
|.gitignore||1 year ago|
|.gitlab-ci.yml||11 months ago|
|CC_BY-SA.txt||5 years ago|
|DEPENDENCIES||10 months ago|
|LICENSE.txt||5 years ago|
|Makefile||1 year ago|
|Makefile.conf||1 year ago|
|README.md||2 years ago|
|clean_sync_leftovers.sh||2 years ago|
|engine_doxygen.conf||2 years ago|
|pEpErr.py||2 years ago|
|release_engine.py||1 year ago|
The p≡p Engine is a Free Software library encapsulating implementations of:
Key Management in the p≡p Engine is based on GnuPG key chains (NetPGP on iOS). Keys are stored in an OpenPGP-compatible format, and can be used for different crypto implementations.
The p≡p Engine sports a two phase trust rating system for messages: In phase one a rating is derived based on channel, crypto and key security. This is named "comm_types". In phase two these ratings are mapped to user-representable values mimicking the semantics of a traffic light.
Abstract Crypto API
The Abstract Crypto API provides functions to encrypt and decrypt data or full messages, without requiring an application programmer to understand the different applied formats and standards.
The p≡p Engine will sport a growing list of message transports, to support any widespread text-based messaging system such as E-Mail, SMS, XMPP and many more.
The p≡p Engine is written in C99 and is expected to run on any platform that conforms to the SUS/POSIX specification. Selected non-SUS platforms are supported as well (such as Microsoft Windows).
Build instructions can be found in the "doc/" subfolder in this repository. The p≡p Engine is not meant to be used in application code directly. Instead, the p≡p Engine is meant to be used in conjunction with a so-called "adapter". An adapter provides an API in a programming language that best accomodates developers in their respective software development ecosystem. So, for example, a Java Native Interface adapter exists for development of apps for the Android mobile operating system, or a .NET adapter exists for development of applications on Microsoft Windows. Various adapters are also available at the link provided for the p≡p Engine's code above.
The p≡p Engine is production-ready. It is under active development by several full-time employees of the p≡p foundation and its partner organizations. The most recent version of the source code can be obtained here: https://pep.foundation/dev/repos. This is the only offical way to obtain a copy of the source code.
First of all, excellent! You can find further information here: https://contribution.pep.foundation/
The p≡p Engine is Copyright 2015-2020 by p≡p foundation, Switzerland. The source code of the p≡p Engine is licensed under the terms of the GNU General Public License version 3. Accompanying documentation is licensed under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) License. Each file includes a notice near its beginning, that indicates the applicable license. If you wish to license the p≡p Engine under different terms, please contact mailto:firstname.lastname@example.org.
_pEp_reallocarray in pgp_sequoia.c is reallocarray from the OpenBSD source. It is copyright (c) 2008 Otto Moerbeek email@example.com with the following permissions: Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
The p≡p foundation and the developers of the p≡p Engine can be reached as detailed here: https://pep.foundation/contact-us/index.html.