updated names

This commit is contained in:
Monica Moniot
2023-08-30 07:37:09 -07:00
parent 8098627ec9
commit d345d673bc
6 changed files with 15 additions and 5 deletions
+10
View File
@@ -1,3 +1,13 @@
target
Cargo.lock
.DS_Store
*.aux
*.fdb_latexmk
*.fls
*.out
*.synctex.gz
*.log
*.xml
*.bcf
*.bbl
*.blg
+2 -2
View File
@@ -13,13 +13,13 @@ Periodic session re-keying uses the [Noise KK](http://noiseprotocol.org/noise.ht
Re-keying does not employ a hybrid exchange. Post-quantum forward secrecy is negotiated only on session startup since the threat model underpinning its use is to protect against very long term data storage and future decryption with quantum computers. Ratcheting causes the result of the initial ephemeral PQ exchange to be mixed into all subsequent session keys, protecting the entire session against a future attacker able to break elliptic curve cryptography.
An in-depth guide to the full protocol specification can be found in the [protocol whitepaper](whitepaper/main.pdf) provided in this repository.
An in-depth guide to the full protocol specification can be found in the [protocol whitepaper](whitepaper/zssp.pdf) provided in this repository.
ZSSP was designed for use in [ZeroTier](https://www.zerotier.com/) but is payload agnostic and open source and can easily be used by other projects. The implementations here are based around generic cryptographic traits that a user can implement in terms of any cryptographic library of API they wish to use. Default implementations in terms of popular Rust cryptography crates are included but can be disabled via feature selection if alternatives are to be used.
This repository includes both a simpler [reference](reference/) implementation that follows the whitepaper very explicitly and a more complex [high performance](performance/) implementation designed for high throughput or use in systems that will manage very large numbers of ZSSP sessions.
See the [ZSSP whitepaper](whitepaper/main.pdf) for extensive documentation and proofs of security.
See the [ZSSP whitepaper](whitepaper/zssp.pdf) for extensive documentation and proofs of security.
## Cryptographic Primitives Used in ZSSP
+1 -1
View File
@@ -168,7 +168,7 @@ fn receive(
context
.send(&session, push_onto_send_queue, TEST_MTU, reply_message)
.unwrap();
// This example does not properly track time so we just call service on every update.
context.service(app.borrow_mut().deref_mut(), |_| Some((push_onto_send_queue, TEST_MTU)));
}
+2 -2
View File
@@ -10,7 +10,7 @@
//!
//! ## Introduction
//!
//! An in-depth guide to the full protocol specification can be found in the [protocol whitepaper](./whitepaper.pdf) provided in this repo. This implementation references it heavily.
//! An in-depth guide to the full protocol specification can be found in the [protocol whitepaper](whitepaper/zssp.pdf) provided in this repo. This implementation references it heavily.
//!
//! ZeroTier Secure Socket Protocol (ZSSP) is a [Noise](http://noiseprotocol.org) protocol implementation using NIST/FIPS/CfSC compliant cryptographic primitives plus post-quantum forward secrecy via [Kyber1024](https://pq-crystals.org/kyber/). It also includes built-in support for fragmentation and defragmentation of large messages with strong resistance against denial of service attacks targeted against the fragmentation protocol.
//!
@@ -20,7 +20,7 @@
//!
//! ZSSP is designed for use in ZeroTier but is payload-agnostic and could easily be adapted for use in other projects.
//!
//! Further information can be found in the ZSSP whitepaper [protocol whitepaper](./whitepaper.pdf).
//! Further information can be found in the ZSSP whitepaper [protocol whitepaper](whitepaper/zssp.pdf).
//!
//! ## Cryptographic Primitives Used
//!
Binary file not shown.