-
Notifications
You must be signed in to change notification settings - Fork 134
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1111 from Shourya742/doc-noise-sv2
Rust docs `noise_sv2`
- Loading branch information
Showing
10 changed files
with
819 additions
and
116 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
|
||
# noise_sv2 | ||
|
||
[![crates.io](https://img.shields.io/crates/v/const_sv2.svg)](https://crates.io/crates/const_sv2) | ||
[![docs.rs](https://docs.rs/const_sv2/badge.svg)](https://docs.rs/const_sv2) | ||
[![rustc+](https://img.shields.io/badge/rustc-1.75.0%2B-lightgrey.svg)](https://blog.rust-lang.org/2023/12/28/Rust-1.75.0.html) | ||
[![license](https://img.shields.io/badge/license-MIT%2FApache--2.0-blue.svg)](https://github.com/stratum-mining/stratum/blob/main/LICENSE.md) | ||
[![codecov](https://codecov.io/gh/stratum-mining/stratum/branch/main/graph/badge.svg?flag=noise_sv2-coverage)](https://codecov.io/gh/stratum-mining/stratum) | ||
|
||
`noise_sv2` is primarily intended to secure communication in the Stratum V2 (Sv2) protocol. It handles the necessary Noise handshakes, encrypts outgoing messages, and decrypts incoming responses, ensuring privacy and integrity across the communication link between Sv2 roles. See the [Protocol Security specification](https://github.com/stratum-mining/sv2-spec/blob/main/04-Protocol-Security.md) for more details. | ||
|
||
## Key Capabilities | ||
* **Secure Communication**: Provides encryption and authentication for messages exchanged between different Sv2 roles. | ||
* **Cipher Support**: Includes support for both `AES-GCM` and `ChaCha20-Poly1305`. | ||
* **Handshake Roles**: Implements the `Initiator` and `Responder` roles required by the Noise handshake, allowing both sides of a connection to establish secure communication. | ||
* **Cryptographic Helpers**: Facilitates the management of cryptographic state and encryption operations. | ||
|
||
## Usage | ||
To include this crate in your project, run: | ||
|
||
```bash | ||
cargo add noise_sv2 | ||
``` | ||
|
||
### Examples | ||
|
||
This crate provides example on establishing a secure line: | ||
|
||
1. **[Noise Handshake Example](https://github.com/stratum-mining/stratum/blob/main/protocols/v2/noise-sv2/examples/handshake.rs)**: | ||
Establish a secure line of communication between an Initiator and Responder via the Noise | ||
protocol, allowing for the encryption and decryption of a secret message. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,68 @@ | ||
// # Noise Protocol Handshake | ||
// | ||
// This example demonstrates how to use the `noise-sv2` crate to establish a Noise handshake | ||
// between and initiator and responder, and encrypt and decrypt a secret message. It showcases how | ||
// to: | ||
// | ||
// - Generate a cryptographic keypair using the `secp256k1` library. | ||
// - Perform a Noise handshake between an initiator and responder. | ||
// - Transition from handshake to secure communication mode. | ||
// - Encrypt a message as the initiator role. | ||
// - Decrypt the message as the responder role. | ||
// | ||
// ## Run | ||
// | ||
// ```sh | ||
// cargo run --example handshake | ||
// ``` | ||
|
||
use noise_sv2::{Initiator, Responder}; | ||
use secp256k1::{Keypair, Parity, Secp256k1}; | ||
|
||
// Even parity used in the Schnorr signature process | ||
const PARITY: Parity = Parity::Even; | ||
// Validity duration of the responder's certificate, seconds | ||
const RESPONDER_CERT_VALIDITY: u32 = 3600; | ||
|
||
// Generates a secp256k1 public/private key pair for the responder. | ||
fn generate_key() -> Keypair { | ||
let secp = Secp256k1::new(); | ||
let (secret_key, _) = secp.generate_keypair(&mut rand::thread_rng()); | ||
let kp = Keypair::from_secret_key(&secp, &secret_key); | ||
if kp.x_only_public_key().1 == PARITY { | ||
kp | ||
} else { | ||
generate_key() | ||
} | ||
} | ||
|
||
fn main() { | ||
let mut secret_message = "Ciao, Mondo!".as_bytes().to_vec(); | ||
|
||
let responder_key_pair = generate_key(); | ||
|
||
let mut initiator = Initiator::new(Some(responder_key_pair.public_key().into())); | ||
let mut responder = Responder::new(responder_key_pair, RESPONDER_CERT_VALIDITY); | ||
|
||
let first_message = initiator | ||
.step_0() | ||
.expect("Initiator failed first step of handshake"); | ||
|
||
let (second_message, mut responder_state) = responder | ||
.step_1(first_message) | ||
.expect("Responder failed second step of handshake"); | ||
|
||
let mut initiator_state = initiator | ||
.step_2(second_message) | ||
.expect("Initiator failed third step of handshake"); | ||
|
||
initiator_state | ||
.encrypt(&mut secret_message) | ||
.expect("Initiator failed to encrypt the secret message"); | ||
assert!(secret_message != "Ciao, Mondo!".as_bytes().to_vec()); | ||
|
||
responder_state | ||
.decrypt(&mut secret_message) | ||
.expect("Responder failed to decrypt the secret message"); | ||
assert!(secret_message == "Ciao, Mondo!".as_bytes().to_vec()); | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.