pretty Easy privacy Overview @ Cyber Economic Forum, January 24 2020

Hernâni Marques (@vecirex) [email protected] (3173 3E0C 598D 3A1C F709 55D6 CB57 3865 2768 F7E9)

p≡p foundation (@pEpFoundation) p≡p Privacy by Default. Problem

● We have Mass Surveillance, now even widespread in countries we considered safe. ● Most still flow between people like postcards→ specifically. ● usage still grows: it won’t die. It’s the most important federated identity system. ● Messages not encrypted and signed by default → for privacy and security (e.g., phishing attacks).

Privacy by Default. Need for pretty Easy privacy

● We need Mass and Mass Anonymization to counter this. ● Citizens, enterprises and public offices have a right to be protected. ● Human Rights must be enforced by technical means (relates to EU GDPR regulations).

Privacy by Default. Need for pretty Easy privacy

● “Good” privacy already exists (in email with PGP/OpenPGP implementations).

● But: Most users are not able to use email encryption tools like GnuPG (properly): usability to be fixed through automation. ● And: Most developers are not able to properly implement (existing) : security to be fixed through abstract API.

● We need not just good, but easy privacy. ● We need Privacy by Default.

Privacy by Default. Philosophy: Cypherpunk & Privacy

“Privacy is necessary for an open society in the electronic age. [...]. A private matter is something one doesn’t want the whole world to know […]. Privacy is the power to selectively reveal oneself to the world.”

Privacy by Default. Approach of pretty Easy privacy

● Privacy by Default is achieved by writing code for automation instead of manuals. – All code available under GNU licenses (as Free Software): https://pep.foundation/dev/ ● are created automatically for each identity (in email: for each account and their aliases). ● Encryption keys are distributed peer-to-peer (P2P) – for emails via attachment (and imported automatically by p≡p clients).

Privacy by Default. Approach of pretty Easy privacy

● No reliance on centralized platforms (in email: key and other servers providing keys). ● Identity verification is possible on a P2P basis through the use of Trustwords. ● p≡p stays compatible and thus is interoperable to existing standards (like OpenPGP). ● Furtherly p≡p, by principle, is agnostic to message transports and cryptography used.

Privacy by Default. Approach of p≡p – organizationally

● p≡p foundation (tax-free) provides a reference implementation of p≡p Engine and Adapters, holding trademarks, owning strategic key components, engaged in standardization, ensuring multi-licensing strategy and requiring code audits – community-controlled: pep.foundation.

● p≡p security (commercial) company as licensee of p≡p foundation’s key components is creating apps / extensions and establishing to serve B2C and B2B markets – selling support and ensuring availablity of money (for dev and profit): pep.security.

Privacy by Default. p≡p software architecture

Plugin Outlook Android iOS app Plugin app App

[tech] Adapter COM Server JNI Objective Adapter Adapter Adapter JSON Adap.

1 Engine p≡p engine Privacy by Default. Running Code: www.pep.software

● p≡p for Outlook (release: add-on) ● p≡p for Android (release: app) ● p≡p for Thunderbird (as Enigmail/p≡p: since Enigmail 2.0 add-on with p≡p integration) ● p≡p for iOS (TestFlight beta)

Privacy by Default. More Code: Development & Support

● p≡p for Apple ● p≡p for Geary (for the GNOME desktop) ● p≡p for Thunderbird (own add-on) ● p≡p for SWIFT (for bank transactions) ● Sequoia PGP library (own alternative to GnuPG) ● Misc support: GNUnet / GNU Taler / GnuPG

Privacy by Default. p≡p for Android

Privacy by Default. p≡p for Outlook

Privacy by Default. p≡p for Thunderbird (Enigmail/p≡p)

Privacy by Default. Vision: Agnosticism in transport /crypto

Privacy by Default. Special feature: p≡p sync

Privacy by Default. Special feature: KeySync (in action: beta)

Privacy by Default. Questions & Rants

● ??? ● ... ● Ask!

Privacy by Default.