README.txt

Welcome to the Encryption Honeypot project. This folder contains everything you need to run a low‑cost, self‑maintaining trap that lures surveillance tools into costly, dead‑end crypto puzzles. The overall theme for February is “Guerrilla Encryption: Making the Cipher the Prize.”

What you’ll find here

    Encrypted conversation bundles (bundle_*.asc) that look like ordinary chat logs but hide tiny OTP fragments.
    A high‑value vault (vault_feb.asc) protected with a strong RSA 4096/Ed25519 key.
    A keys/ subfolder with the public keys you need to verify signatures.
    Simple scripts in the scripts/ directory that generate keys, create fragments, and assemble the puzzle network.

How to use the honeypot

    Deploy the web folder – copy the entire honeypot/ directory to the document root of your web server (e.g., /var/www/html/).
    Enable HTTPS – obtain a free Let’s Encrypt certificate with certbot and reload the server.
    Set up expiration – the create_self_destruct.sh script installs a cron job that removes old bundles after the date shown in each filename and returns a “410 Gone” response.
    Optional country gating – run geoip_gate.sh to restrict access to selected countries; the script adds the necessary nginx or Apache configuration.

What to expect
When an analyst or automated scanner visits the directory they will see a list of encrypted files, each labeled with an expiration date. The easy‑to‑crack RSA 2048 bundles provide a quick win, encouraging deeper exploration. More advanced rooms require multiple fragments or a costly Diffie‑Hellman fallback, draining CPU cycles. The vault, protected by the stronger key, offers the biggest “prize” but also the greatest computational expense.

Help and feedback
If you run into any issues, check the docs/INSTRUCTIONS.md file for detailed step‑by‑step guidance, or reach out via the contact information in docs/CONTACT.txt.

Enjoy building your own guerrilla‑encryption trap, and may the cipher be ever in your favor.