▓█████  ███▄    █  ▄████▄   ██▀███ ▓██   ██▓ ██▓███  ▄▄▄█████▓
▓█   ▀  ██ ▀█   █ ▒██▀ ▀█  ▓██ ▒ ██▒▒██  ██▒▓██░  ██▒▓  ██▒ ▓▒
▒███   ▓██  ▀█ ██▒▒▓█    ▄ ▓██ ░▄█ ▒ ▒██ ██░▓██░ ██▓▒▒ ▓██░ ▒░
▒▓█  ▄ ▓██▒  ▐▌██▒▒▓▓▄ ▄██▒▒██▀▀█▄   ░ ▐██▓░▒██▄█▓▒ ▒░ ▓██▓ ░ 
░▒████▒▒██░   ▓██░▒ ▓███▀ ░░██▓ ▒██▒ ░ ██▒▓░▒██▒ ░  ░  ▒██▒ ░ 
░░ ▒░ ░░ ▒░   ▒ ▒ ░ ░▒ ▒  ░░ ▒▓ ░▒▓░  ██▒▒▒ ▒▓▒░ ░  ░  ▒ ░░   
 ░ ░  ░░ ░░   ░ ▒░  ░  ▒     ░▒ ░ ▒░▓██ ░▒░ ░▒ ░         ░    
   ░      ░   ░ ░ ░          ░░   ░ ▒ ▒ ░░  ░░         ░      
   ░  ░         ░ ░ ░         ░     ░ ░                       
                  ░                 ░ ░                       
==============================================================

To access our main server, please email us your hash so we can grant you access.

HASH    : A95E0C74EA743324E8FDE710FD34BCB0D5D65B791CC1B21EE4A062BD66602D9E
IP      : 104.244.77.14
PORT    : 10101
CONTACT : hello@e-n-c-r-y-p-t.cc

Peer Connection Requirements:
|
|- For a peer to successfully connect to the system, its IP address must satisfy the following conditions:
|   |-> Present in allowed_hashes.txt: The SHA-256 hash of the peer's IP address must be listed in the allowed_hashes.txt file.
|   |-> Present in trusted_hashes.txt: The same SHA-256 hash must also be found in the trusted_hashes.txt file.
|   |-> Both conditions must be met simultaneously. If the peer's IP hash is absent from either file, the connection will be denied.
|
|- This dual-check mechanism ensures that only trusted and explicitly allowed peers can establish a connection, 
  enhancing the security and integrity of the network.
				  
==============================================================

🔐 
A peer-to-peer application that securely exchanges random data between peers using TLS encryption.
			
==============================================================
			
🚀 
Overview

This project implements a TLS-encrypted P2P communication system where each peer authenticates the other using a custom challenge-response mechanism based on X.509 certificates exchanged after the TLS handshake. 

The system includes additional security and privacy features such as:

    🔄 Post-handshake certificate exchange (manual verification)
    🛡️ Challenge-response authentication using public/private key cryptography
    🎭 Continuous transmission of random, obfuscated data to thwart traffic analysis and fingerprinting
    🔗 Support for asynchronous send/receive over secure TLS sockets

==============================================================

⚙️ 
Key Features

1. 🔐 TLS Connection Setup

    Establishes a secure TLS connection between peers.
    Uses OpenSSL for encrypted transport.
    After the TLS handshake completes, peers exchange their public certificates.

2. 📄 Post-Handshake Certificate Exchange

    Unlike typical TLS mutual authentication, certificates are exchanged after TLS is established.
    Allows flexible certificate management without requiring TLS client authentication during handshake.
    Peers send their certificates over the established TLS channel.

3. 🔏 Custom Challenge-Response Authentication

    Once each peer has the other's certificate, it generates a random challenge (nonce).
    The challenge is sent to the peer, who must sign it with its private key.
    The signature is sent back and verified against the public key in the received certificate.
    Only a peer that holds the private key corresponding to the public certificate can successfully authenticate.

4. 🎲 Obfuscated Random Data Transmission

    To prevent traffic analysis and timing attacks, peers continuously send randomly generated obfuscated data.
    This data is indistinguishable from normal traffic but carries no meaningful payload.
    Helps to mask communication patterns and defend against fingerprinting.

5. 💬 Communication Protocol

    After successful mutual authentication, peers can securely exchange randomly generated obfuscated data.

==============================================================
	
🏗️ How it works

        Peer A                                              Peer B
   ┌───────────────┐                                  ┌───────────────┐
   │ TLS Handshake │  <---------------------------->  │ TLS Handshake │
   │ (ClientHello) │                                  │ (ServerHello) │
   └───────────────┘                                  └───────────────┘
          │                                                   │
          │<----- Post-handshake certificate exchange ------->│
          │                                                   │
          │------------- Challenge (nonce) ------------------>|
          │<------------ Challenge signature response --------|
          │                                                   │
          │   Verify signature against peer's public key      |
          │                                                   │
          │<----------- Secure, authenticated comm ---------->│
          │                                                   │
          │<------- Random obfuscated data streams ---------->│