officially -Ghost in the Wires *
BPQ + w3myPQ
⚠️ Configuration Required:
The WordPress permalink structure must not be set to “Plain” for BPQ file sharing to work.
THE EASY GUIDE TO TOTAL SECRET FILE SHARING
Welcome! This guide should teaches you how to use w3mypq – WordPress plugin | WordPress.org and BPQ together—a system that grants you 100% sovereignty over your files, delivering absolute privacy and total anonymity. This is not Signal, Telegram, or any other mainstream application claiming complete security. This is a radically different approach to data protection, offering a level of security unlike anything else available on the web.
Provided your device is not already compromised, no company, server administrator, or hacker can ever view your private data. It is a true Zero-Trust system.
- The WordPress Site(s): Acts ONLY as a blind mailbox folder.
- BennyPQ: Runs locally on your computer to do the secret locking.
STEP 1: SWAP YOUR PUBLIC KEYS PRIVATELY
Before you send a file, you and your friends/recipients must exchange yours “Public Keys”.
- Open your key generator screen and create a keypair.
- Download generated keys.
- Open with a text editor the Public ML-KEM key .txt file and just before the starting
-----BEGIN PUBLIC KEY-----75a1097f600f0449478025724 ....
add/prepend your WordPress email or username to the Public key (if you want to be “decentralized” all over different WordPress sites where you do not own the same username may use the email) like this:
me@you.us-----BEGIN PUBLIC KEY-----75a1097f600f0449478025724 ....
or using an username
myLoginUsername-----BEGIN PUBLIC KEY-----75a1097f600f0449478025724 ....
Now you can email your PUBLIC key file to your contacts (that maybe you know, but maybe not, because they could be, like you, anonymous).
Request your contacts/recipients to email their PUBLIC KEM key file to you, ensuring that they include their associated email address or username prepended to the key, if either of you wishes to use the WordPress gateway rather than just a private email exchange.
Save those txt files containing Public recipients keys into a folder maybe, naming each file like mari_public_Kem.txt or Andrea_public_key.txt etc as more you like so when you have to encrypt and share a secret file you can loads recipients immediately and without errors.
⚠️ CRITICAL SAFETY RULE: Never, ever share your PRIVATE key.
Store your Private KEM key securely on your local hard drive using the Cincia keys vault (get keys screen).
⚠️ If you lose your Private ML-KEM key your ciphered data becomes permanently unrecoverable.
STEP 2: SHARING FILES
Users who want to share ghost payloads via the WordPress endpoint—where WordPress acts strictly as a transport mail server—must register on that WordPress site (where a w3myPQ is installed) using the exact same username and/or email address they use to distribute the data. Additionally, users must load the Public ML-DSA key associated with their ML-DSA Private key into the user profile of the specific WordPress site (that run w3myPQ) they want to send data to.
This Public ML-DSA key is required in the profile to facilitate the handshake between BennyPQ (BPQ) and WordPress, allowing the server to verify that the uploading user is legitimate. On the client side, the Private ML-DSA key entered into the BPQ share screen is used locally to generate the cryptographic signature required for this handshake, ensuring your private key never leaves your device.
To share a ciphered file, a user must load the recipient’s ML-KEM Public Key(s) into the Encrypt screen. If a ciphered payload is not yet ready, encrypt the files first, and then click the Remote Hosting Panel button. Load the required data and share the payload. This process can be executed while operating behind Tor, proxies, VPNs, or other anonymizing layers, maybe mixed.
It functions globally and, with proper care, allows you to operate like a ghost on the web.
How the Zero-Trust architectural flow works:
By leveraging a zero-knowledge cryptographic handshake, users can stream encrypted chunked archives from their local hard drives straight into the server’s REST API gateway via normal connection or behind TOR, VPNs, Proxies.
The server automatically validates user permissions, enforces rolling storage quotas, and authenticates the sender’s identity via a pure-PHP lattice verification process before a single byte touches the secure disk vault.
== Decentralized Architecture ==
The w3myPQ ecosystem is completely decentralized. Identity is cryptographically bound to the user’s post-quantum key pair, rather than locked into a centralized database. A user sharing a payload via email tied to their key can use that same email and key pair to share the identical or a completely different payload across multiple independent WordPress sites—provided those sites have installed w3myPQ and have the matching ML-DSA public key loaded.
This allows for seamless, multi-node cryptographic federation across separate, independent server vaults worldwide.
== Zero-Trust & Anonymity Pipeline ==
Because encryption happens entirely client-side, the system operates on a strict Zero-Trust model. You do not need to trust the network, the server, or even the system administrator.
Users having the same email and KEM public keys loaded into different WordPress nodes can receive ciphered files securely into any independent WordPress vault. For maximum security, users can share their public keys via email with each other privately. The server merely facilitates the chunked transport layer, remaining completely blind to the underlying protected payload data.
== Prevention of Public Key Injection & Impersonation ==
To completely eliminate the risk of public key injection and user impersonation by a compromised server or a malicious administrator, or a man in the middle attack, users can share files using the BPQ standalone client integration gateway. BennyPQ uses the exact same core cryptographic code as w3myPQ.
However, since it is a standalone file loaded locally and NOT served by WordPress, an untrusted administrator or compromised server has no way to tamper with or modify the source code.
This ensures that the integrity of your key validations and encryption routines remains fully secure in your local browser sandbox, regardless of the hosting environment’s status.
* Ghost in the Wires refers to the title of the famous hacker Kevin Mitnick‘s book.
