Code STATUS: LOGGED

OmniShell

OmniShell is my sandbox for testing resilient communication. I wanted to build something that could talk through Tor, Bluetooth, or even satellite if needed, while keeping everything encrypted end-to-end. It’s a CLI tool because at the core of real privacy, you don’t need a fancy UI—you just need the raw data to be safe.

Core Stack

#Rust#Cryptography#P2P#Security
VIEW SOURCE
omnishell_daemon_v0.4

[SYSTEM] Initializing DH-KEA Exchange...

[SYSTEM] Key verified. Buffer established.

Sagheer: Send encrypted packet 0xA4...

Remote: [REDACTED BY AES-256]

> Listening on port 4433...

The Intent

Most "secure" messengers still use central servers that can be monitored. I wanted to remove that middleman entirely and rely on peer-to-peer encryption.

System Schematic

graph TD A[Source Node] -->|RSA-Handshake| B(P2P Bridge) B -->|Encrypted Payload| C{Transport Layer} C -->|Tor| D[Onion Network] C -->|BLE| E[Local Peer] D --> F[Destination] E --> F

The Build

I used Rust to build a transport-agnostic bridge. The code handles the encryption, and you just point it at a socket—whether that’s a local serial port or an Onion address.

Reflections

Cryptography is honest. If you mess up one bit in the key, nothing works. It taught me extremely disciplined debugging.