Secure exchange
P2P Chat
Direct Encrypted ExchangeWhen trust is personal, remove the unnecessary middleman.
A simple encrypted P2P connection workflow using host/listener and client roles, a shared generated key, and a dedicated p2pchat_files folder for transfers.
Plain English
P2P Chat creates a direct encrypted connection between a host and client so they can exchange messages and files without third-party servers.
What it teaches
- direct secure exchange
- shared-secret handling
- host/client setup
- safe file transfer boundaries
Use when
- Two trusted parties need direct encrypted chat
- Files should move without cloud storage
- Operators need a simple no-server transfer path
What it observes
- Host IP and port
- Encryption type
- Shared key match
- Allowed IP and connected state
Requirements
- Host and client must choose the same encryption type
- Shared generated key must be delivered out-of-band
- Files must be placed inside p2pchat_files
- Network/firewall must allow the chosen host port
Manual-backed details
- Recommended encryption options are AES-256-GCM or ChaCha20-Poly1305.
- The listener only accepts a connection that presents the exact key and connects from an allowed IP.
- Files are sent from the chat window with /send filename.ext and land in the recipient's p2pchat_files folder.
Next step
Have one side host, generate a key, share IP/port/key out-of-band, connect from the client, then transfer only files staged in p2pchat_files.
