Keybox Telegram Here
Write-Up: Keybox Telegram Bot – Secure Credential Delivery
Self‑Hosting the Bot
- Create a new bot via @BotFather on Telegram.
- Deploy the bot code (Docker or Python) on your own server.
- Set environment variables:
DB_URL, ENCRYPTION_SALT, ADMIN_IDS.
- Run
docker-compose up -d
Limitations
- Telegram itself is not end‑to‑encrypted by default for bot chats (use secret chats with a wrapper, or rely on client‑side crypto).
- Metadata (key names, timestamps) is visible to the bot operator – avoid revealing secrets in key names.
- Not a replacement for HashiCorp Vault in large orgs, but perfect for small teams or individuals.
How It Works
- User authenticates with the bot using a master passphrase (never stored).
- Client‑side encryption encrypts the key+metadata before sending to the bot.
- Bot stores the encrypted blob in a database (no plaintext keys ever touch the server).
- On request, the bot returns the encrypted blob → decrypted only on the user’s device.
For sharing, the bot generates a one‑time, expiring decryption token tied to the recipient’s Telegram ID.