OmniTransfer
Data goes from your machine to the other. Through no one. Encrypted with crypto that has zero CVEs — because it doesn't use OpenSSL.
The Problem
Secure file transfer depends on OpenSSL or SSH — both with long histories of critical CVEs (Heartbleed, LogJam, etc.). Cloud-based solutions route data through third-party servers. Every intermediary is a potential interception point. Every dependency is inherited vulnerability.
The Solution
OmniTransfer sends files point-to-point with bare-metal cryptography. No OpenSSL. No SSH. No cloud relay. The encryption is implemented directly in the ~25KB binary — it doesn't inherit Heartbleed, doesn't inherit LogJam, doesn't inherit anything.
Why Bare-Metal Matters
Conventional encrypted transfer relies on OpenSSL — a 500K+ line codebase with a history of critical vulnerabilities. OmniTransfer implements encryption in bare-metal assembly with zero external code. The entire cryptographic stack is auditable in the ~25KB binary.
Technical Specifications
| Feature | Value |
|---|---|
| Binary Size | ~25KB |
| Encryption | Bare-metal crypto (no OpenSSL) |
| Transfer Mode | Point-to-point (no intermediary servers) |
| Dependencies | None |
| Cloud Relay | None — direct connection |
| Inherited CVEs | 0 (no OpenSSL, no SSH) |
| Protocol | Custom encrypted P2P |
Comparison
| OmniTransfer | SFTP/SCP | WeTransfer/Dropbox | |
|---|---|---|---|
| Size | ~25KB | OpenSSH 10MB+ | Cloud service |
| Intermediary servers | None | None (direct) | Yes (cloud) |
| Dependencies | None | OpenSSH, OpenSSL, libc | Browser + internet |
| Data passes through cloud | Never | No | Always |
| Inherited crypto CVEs | 0 | OpenSSL CVEs | Unknown (proprietary) |
| Offline operation | Yes (LAN) | Yes | No |
Use Cases
HIPAA File Transfer
Transfer patient records between hospitals without data passing through cloud servers. Point-to-point encryption with zero dependency CVEs.
Legal Document Exchange
M&A documents transferred directly between firms. No Dropbox. No email attachments. No cloud trail. Attorney-client privilege maintained by architecture.
Financial Reporting
Regulatory reports transferred between institutions with cryptographic guarantees and zero intermediary exposure.