Skip to content
peer-to-peer communications library for Rust based on QUIC protocol
Branch: master
Clone or download

README.md

quic-p2p

Crate Documentation Linux/macOS/Windows
Documentation Build Status
MaidSafe website SAFE Dev Forum SAFE Network Forum

Overview

This library provides a mechanism for peers on P2P networks to communicate securely. It also allows the network peers to re-join the network without requiring them to re-connect to any known peers. These peers such as hard coded peers or DNS defined peers as these are obviously a security concern and a centralised set of peers that can easily be attacked or even torn down. There are several informative posts describing both QUIC and TLS 1.3.

The IETF draft specification Cloudflare intro to quic cloudflare intro to TLS 1.3

These are highly recommended to be able to better understand this library, in particular the Cloudflare blog posts (10 minute read).

Encryption of connections

QUIC proved connection security via the use of TLS 1.3. This library allows 3 different connection types with regard to encryption and validation.

  1. Require peers have certificates from an agreed certificate authority.
  2. Allow use of a private certificate authority.
  3. Allow no identity validation of peers, but do encrypt connections.

This should satisfy the requirements of many P2P networks, whether they trust any clearnet certificate authority (which may be a centralised attack source) or whether they pass the identity management up to a different layer to validate identities and simply use quic-p2p as a secured network in terms of encrypted connections.

Bootstrap Cache

quic-p2p will save any endpoints and certificates of nodes that are connectible without any setup such as is required via NAT hole punching. The most recently connected 200 nodes are stored and these are then used to re-join the network after any restart.

Connectivity types

quic-p2p sets 2 connection types when in P2P mode. This allows the connections to be defined as:

  1. A bi-directional connection.

  2. A uni-directional connection.

Where 1 allows connections from consumers of the network, such as clients or perhaps P2P nodes who are simply obtaining information, such as bootstrapping, 2 is used where the network is allowing another P2P worker. These peers must be both able to connect and be able to be connected to. Using a uni-directional stream per connection forces the node to confirm both incoming and outgoing connectivity is available.

A peer my also use a bi-directional connection where it is using STUN or TURN to make that connection. It has to however introduce itself as a Client and not a Node as Nodes are always checked for reverse connectivity to them.

IP Spoof defence

This library enables stateless-retry to defend against IP spoofing. This is achieved by sending a token back to the connecting node which must be returned. quic also defines a protocol negotiation process that defend against many attacks by confirming the acceptable protocols. This is defined here.

TODO

  • Hole punching for NAT traversal
  • Support for async/await syntax
  • Benchmarks and more examples

License

This SAFE Network library is dual-licensed under the Modified BSD (LICENSE-BSD https://opensource.org/licenses/BSD-3-Clause) or the MIT license (LICENSE-MIT http://opensource.org/licenses/MIT) at your option.

Contribution

Copyrights in the SAFE Network are retained by their contributors. No copyright assignment is required to contribute to this project.

You can’t perform that action at this time.