Project QRE Blog

Updates, Research, and Technical Deep Dives

Privacy Research, Encryption Updates & Security Engineering

The QRE Privacy Toolkit Blog covers technical deep dives into file encryption, password security, secure deletion algorithms, and Zero-Knowledge architecture. Here we document our development process, cryptographic design decisions, Android integration milestones, and security research insights.

Our mission is to build a local-first, privacy-respecting toolkit that eliminates cloud dependency while maintaining military-grade encryption standards. Follow along for release announcements, technical breakdowns, and future roadmap updates.

Time-Lock Encryption in QRE v2.7.6 — A Technical Deep Dive

A complete technical walkthrough of the new Time-Lock Encryption feature introduced in v2.7.6. Covers the cryptographic model, the V7 file format with its fixed 4 KB header region, the two-layer clock-manipulation defense combining NTP verification (median of three servers, no external crates) and an in-file ratchet mechanism that persists the highest witnessed timestamp directly inside the .qre file — no sidecar files, no third parties, and no internet connection required for locking.

Read more »

How QRE Privacy Toolkit Protects Your Vault: Authentication System Deep Dive

A complete walkthrough of QRE Privacy Toolkit’s authentication system — from first-time vault creation through daily unlock, session management, and password recovery. Covers the envelope encryption key hierarchy, Argon2id KDF parameters, AES-256-GCM authenticated encryption, atomic keychain writes, in-memory zeroization, and the full threat model. No prior cryptography knowledge required.

Read more »

Security Hardening Report: QRE Privacy Toolkit v2.6.9

A full walkthrough of the security hardening work completed for v2.6.9 — including rand 0.9 migration, cargo-audit and cargo-deny triage, Clippy hardening, dead code removal, panic elimination across 34 production call sites, a critical filesystem scope fix that removed unrestricted "**" access, and the addition of a fuzz testing pipeline targeting the decrypt attack surface.

Read more »