Repository navigation
v0.94.0 — encrypted mission backups (optional)
Try it at rangertrak.org. New here? Start at rangertrak.com.
You can now put a passphrase on a mission backup
Mission → Back up mission asks for one. That file is the one worth protecting: it carries your whole roster — names, personal phone numbers, photos, call signs — and every field report, and it's the file designed to travel onto a stick or into an email.
Leaving the passphrase blank writes exactly the same plain file as before. That's still the default, and older backups keep opening with no prompt at all. Nothing you already have stops working.
If you set one, you'll be asked to type it a second time — because a mistyped passphrase isn't discovered until the day you actually need the backup.
⚠️ A forgotten passphrase cannot be recovered. No server, no reset, nobody to ask — the same property that keeps your data off the Internet. Keep an unencrypted copy somewhere physically secure, or store the passphrase the way your agency stores other credentials.
Encrypted backups save as .rtenc.json so you can spot them in a folder.
What this does and doesn't protect
It protects a file that has left your device: a lost laptop, a misplaced USB stick, an email forwarded further than intended.
It does not encrypt the data sitting in your browser on an unlocked device. That's still in the clear, and the roster warning in the Field Guide still applies. Encrypting storage is a larger change and is planned separately.
For the technically inclined
AES-GCM-256 with PBKDF2-SHA256 at OWASP's current iteration floor, a fresh random salt and IV per file, via the browser's native Web Crypto — no crypto library added. The iteration count is stored in the file and read back on open, so it can be raised later without stranding backups written today. AES-GCM is authenticated, so a corrupted or altered file fails cleanly instead of restoring plausible nonsense.
Full detail in CHANGELOG.md and ARCHITECTURE.md.