8
3
Fork
You've already forked pEpEngine
0
The p≡p Engine https://pep-project.org
  • C 87.5%
  • C++ 11.4%
  • Python 0.5%
  • Makefile 0.2%
  • Shell 0.2%
  • Other 0.1%
Find a file
2026年06月16日 18:07:31 +02:00
.gitlab-ci-files CI: use Docker-in-Docker instead of KVM 2023年03月16日 21:04:02 -05:00
api minor changes 2026年01月16日 16:21:07 +01:00
asn.1 minor changes 2026年01月16日 16:21:07 +01:00
build-android minor changes 2026年01月16日 16:21:07 +01:00
build-mac Correct path to the generated asn.1 source files 2026年03月11日 19:45:58 +01:00
build-windows minor changes 2026年01月16日 16:21:07 +01:00
codegen fix codegen/gen_statemachine.ysl2 , covering the case in which one has the CPP macro NDEBUG #define'd by hand with the default DEBUG setting 2026年03月05日 13:57:25 +01:00
db build system: fix trivial error 2026年05月19日 16:43:20 +02:00
doc minor changes 2026年01月16日 16:21:07 +01:00
old add release script 2022年11月30日 22:10:20 +01:00
pEpMIME minor changes 2026年01月16日 16:21:07 +01:00
scripts documentation and comments: update URLs, now that the organisation on codeberg has been renamed from "pEp-foundation" to "pEp" 2023年12月07日 16:12:07 +01:00
src revert the fix for #201 in order to fix #236 2026年06月16日 18:07:31 +02:00
test engine-236: test suite code 2026年06月16日 18:07:31 +02:00
.gitignore ignore test suite core files for git status 2025年12月05日 13:48:09 +01:00
.gitlab-ci.yml Build: Rename local.conf to build.conf globally 2023年08月29日 17:01:05 +02:00
BUILD-DEPENDENCIES update build dependencies, new BUILD-DEPENDENCIES file 2024年05月30日 16:28:48 +02:00
build.conf.example minor changes 2026年01月16日 16:21:07 +01:00
CC_BY-SA.txt
clean_sync_leftovers.sh adding trust sync files to clean_sync_leftovers.sh 2020年04月27日 19:27:23 +02:00
DEPENDENCIES correct DEPENDENCIES 2024年06月11日 14:47:31 +02:00
engine_doxygen.conf remove _PEP_SQLITE_DEBUG support... 2023年05月09日 14:34:14 +02:00
LICENSE.txt upgrade management database to version 20; minor factoring and internal changes 2026年01月07日 15:23:49 +01:00
Makefile Add target install_headers_only 2026年01月26日 16:42:12 +01:00
Makefile.conf darwin: do not define PER_MACHINE_DIRECTORY in Machine.conf 2026年05月19日 14:56:40 +02:00
NEWS revert the fix for #201 in order to fix #236 2026年06月16日 18:07:31 +02:00
pEp-engine-print-log update notices 2023年12月11日 17:40:56 +01:00
pEpErr.py ENGINE-633: fixed some bugs with key removal for pEp users if expired, but am stuck on some TOFU cases, so progress is stalled somewhat. 2020年09月03日 09:16:22 +02:00
README.md minor changes 2026年01月16日 16:21:07 +01:00
README.WINDOWS add some windows documentation and comments 2022年11月03日 14:47:25 +01:00
release improve Engine version information constants 2026年03月11日 10:45:24 +01:00
THANKS documentation: punctuation 2023年01月30日 17:21:47 +01:00

What is the p≡p Engine?

The p≡p Engine is a Free Software library encapsulating implementations of:

  • Key Management

    The p≡p Engine automatically manages keys using a pluggable crypto backend. The currently implemented backend is based on Sequoia PGP, and uses OpenPGP-format keys.

    p≡p for Email is interoperable with OpenPGP.

  • Trust Rating

    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.

  • Message Transports

    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 C17 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).

How can I use the p≡p Engine?

The entire p≡p stack including the p≡p Engine can be built with the pEp-build script https://codeberg.org/pEp/pEp-build/ on Unix machines.

(Some older build documentation, no longer supported or recommended, is also still available at https://codeberg.org/pEp/pEpEngine/wiki/adapter%3A%3Aadapter-build-instructions-version-3-x-draft )

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.

What is the current state of the project?

The p≡p Engine is production-ready. It is under active development by p≡p Apps. The most recent version of the source code can be obtained here: https://codeberg.org/pEp/. This is the only offical way to obtain a copy of the source code.

I would like to contribute to the p≡p Engine or a related project, where do I start?

First of all, excellent! You can find further information here: https://pep-project.org

Legal notes

The p≡p Engine is Copyright 2015-2025 by p≡p Apps, 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 us.

src/pEp_rmd160.c is adapted from LibTomCrypt by Tom St Denis and contributors, which was released by its authors into the public domain.

Contact

The p≡p team including the developers of the p≡p Engine can be reached as detailed at https://pep-project.org.