Peergos is building the next web - the private web, where end users are in control. Imagine web apps being secure by default and unable to track you. Imagine being able to control exactly what personal data each web app can see. Imagine never having to log in to an app ever again. You own your data and decide where it is stored and who can see it. At Peergos, we believe that privacy is a fundamental human right and we want to make it easy for everyone to interact online in ways that respect this right.
The foundation of Peergos is a peer-to-peer encrypted global filesystem with fine-grained access control designed to be resistant to surveillance of data content or friendship graphs. It will have a secure messenger, with optional interoperability with email, and a totally private and secure social network, where users are in control of who sees what (executed cryptographically). Our motto at Peergos is, "Control your data, control your destiny."
The name Peergos comes from the Greek word Πύργος (Pyrgos), which means stronghold or tower, but phonetically spelt with the nice connection to being peer-to-peer. Pronuniation: peer-goss (as in gossip).
Want to try it out now? Here's our demo https://demo.peergos.net.
Our beta is live at https://beta.peergos.net/. There are a limited number of free accounts available.
You can read more detail about our features and architecture in our tech book.
The slides of a talk introducing Peergos are here
Architecture talk at IPFS Lab Day:
Introduction and 2020 update:
Introduction:
Tour:
If you would like to support Peergos development, then please make a
recurring donation less than 100 EUR per week
or a
Cure53 conducted an audit of Peergos in June 2019. The final report is here.
There is a public chat room for Peergos on Matrix.
- To allow individuals to securely and privately store files in a peer to peer network which has no central node and is generally difficult to disrupt or surveil
- To allow secure sharing of files with other users of the network without visible meta-data (who shares with who)
- To have a beautiful user interface that any computer or mobile user can understand
- To enable a new secure form of email
- To be independent of the central TLS Certificate Authority trust architecture
- Self hostable - A user should be able to easily run Peergos on a machine in their home and get their own Peergos storage space, and social communication platform from it.
- A secure web interface
- To enable secure real time chat
- Plausibly deniable dual login to an account, ala Truecrypt
- Optional use of U2F for securing login
- Peergos does not provide anonymity, yet. Anonymity can be achieved by creating and only ever accessing a User account over Tor
1.0 Layers of architecture
- 1: Peer-to-peer and data layer - IPFS provides the data storage, routing and retrieval. A User must have at least one peergos instance storing their data for it to be available.
- 2: Authorization Layer - a key pair controls who is able to modify parts of the file system (every write is signed)
- 3: Data storage - controlled by a given public key there is a merkle-champ of encrypted chunks under random labels, without any cross links visible to the network (the network can't deduce the size of files)
- 4: Encryption - Strong encryption is done on the user's machine using TweetNaCl, with each 5MiB chunk of a file being encrypted independently.
- 5: Social layer implementing the concept of following or being friends with another user, without exposing the friend network to anyone.
- 5: Sharing - Secure cryptographic sharing of files with friends.
2.0 Language
- The IPFS layer is currently coded in Go
- The server is coded to run on JVM to get portability and speed, predominantly Java
- The web interface is mostly coded in Java and cross compiled to Javascript, with the exception of the tweetnacl and scrypt libraries, and a small amount of GUI code in JS for Vue.js.
- Apps are written in HTML5
3.0 Nodes
- There is a pki node which ensures unique usernames using a structure similar to certificate transparency. This data is mirrored on every peergos server. Eventually we might put this small amount of data in a blockchain for full decentralization.
- A new node contacts any public Peergos server to join the network
4.0 Trust
- New versions of the software will be delivered through Peergos itself. (Able to be turned off by the user if desired)
- A user who trusts a public Peergos server (and the SSL Certificate authority chain) can use the web interface over TLS
- A less trusting user can run a Peergos server on their own machine and use the web interface over localhost
- A more paranoid user can run a Peergos server on their own machine and use the CLI or the fuse binding
- Servers are trustless - your data and metadata cannot be exposed even if your server is compromised (assuming your client is not compromised)
- IPFS itself is not trusted and all data stored or retrieved from it is verified externally.
- The data store (which may not be ipfs directly, but S3 compatible service for example) is also not trusted
4.0 Logging in
- A user's username is used along with a random salt and the hash of their password and run through scrypt (with parameters 17, 8, 1, 96, though users can choose harder parameters if desired) to generate a symmetric key, an encrypting keypair and a signing keypair. This means that a user can log in from any machine without transfering any keys, and also that their keys are protected from a brute force attack (see slides above for cost estimate).
5.0 Encryption
- private keys never leave client node, a random symmetric key is generated for every file (explicitly not convergent encryption, which leaks information)
5.1 Post-quantum encryption
- Files that haven't been shared with another user are already resistant to quantum computer based attacks. This is because the operations to decrypt them from logging in, to seeing plain-text, include only hashing and symmetric encryption, both of which are currently believed to not be significantly weakened with a quantum computer.
- Files that have been shared between users are, currently, vulnerable to a large enough quantum computer if an attacker is able to log the initial follow requests sent between the users (before the user retrieves and deletes them). This will be replaced with a post-quantum asymmetric algorithm as soon as a clear candidate arrives.
6.0 Friend network
- Anyone can send anyone else a "follow request". This amounts to "following" someone and is a one way protocol. This is stored in the target user's server, but the server cannot see who is sending the friend request (it is cryptographically blinded).
- The target user can respond to friend requests with their own friend request to make it bi-directional (the usual concept of a friend).
- Once onion routing is integrated, there will be no way for an attacker (or us) to deduce the friendship graph (who is friends with who).
7.0 Sharing of a file (with another user, through a secret link, or publicly)
- Once user A is being followed by user B, then A can share files with user B (B can revoke their following at any time)
- File access control is based on cryptree system used by Wuala
- a link can be generated to a file or a folder which can be shared with anyone through any medium. A link is of the form https://demo.peergos.net/#KEY_MATERIAL which has the property that even the link doesn't leak the file contents to the network, as the key material after the # is not sent to the server, but interpreted locally in the browser.
- a user can publish a capability to a file or folder they control which makes it publicly visible
Instructions for self hosting will be updated once it is supported.
In the meantime you can experiment (BEWARE: we occasionally need to delete the data on this test network, so don't use it as your only copy of anything) with running your own Peergos server in our demo network by downloading a release from https://beta.peergos.net/public/peergos/releases
You will need Java >= 11 installed.
Run Peergos with:
java -jar Peergos.jar daemon -pki-node-id QmdM1TrjBJnYzzESATtrrMNPAtjJdqfcV2vF1kM39DY7cc -peergos.identity.hash z59vuwzfFDoqvC6R5QBV4tXx6ZK3SytpvvcjKnWD2VXZXhxDbFq7Fuu -log-to-console true
You can then access the web interface over http:/localhost:8000/
Note that whichever Peergos server you sign up through will be storing your data (we plan to enable migration later), so if you don't intend on leaving your Peergos server running permanently, then we recommend signing up on https://demo.peergos.net and then you can log in through a local Peergos instance and all your data will magically end up on the demo.peergos.net server.
There are a range of commands available from a command line. You can run -help to find the available commands or details on any command. Most users should only need the daemon and shell commands, and maybe fuse. You can use the migrate command to move all your data to a new server (where the command is run).
>> java -Djava.library.path=native-lib -jar Peergos.jar -help
Main: Run a Peergos command
Sub commands:
daemon: The user facing Peergos server
shell: An interactive command-line-interface to a Peergos server.
fuse: Mount a Peergos user's filesystem natively
quota: Manage quota of users on this server
server-msg: Send and receive messages to/from users of this server
gateway: Serve websites directly from Peergos
migrate: Move a Peergos account to this server.
ipfs: Install, configure and start IPFS daemon
pki: Start the Peergos PKI Server that has already been bootstrapped
pki-init: Bootstrap and start the Peergos PKI Server
Requires jdk11 and ant to build. Use the following to install dependencies:
sudo apt-get install ant
sudo apt-get install openjdk-11-jdkbrew install ant # installs openjdk as a dependency
ant -version
Apache Ant(TM) version 1.10.8 compiled on May 10 2020Note that this doesn't include any web ui, for the full build including the web interface build https://github.com/peergos/web-ui
ant distant gwtcYou need to have ant-optional installed:
sudo apt-get install ant-optionalNothing additional is needed for the ant package on macOS.
Running tests will install and configure the correct version of IPFS automatically, run the daemon, and terminate it afterwards.
ant testThe ant compile target will only compile sources in src/peergos/{client,server,shared} folders.