🔒 ATLOCK v5.0
AN AKHOURI SYSTEMS PRODUCT
Designed for Windows. Engineered with Python. Built with a security-first mindset.
You have seen ATLOCK v4.0.
Now, let's talk about what comes next.
⚫ NOT A RELEASE. A FIRST LOOK.
Every major product evolution starts somewhere.
Sometimes, it begins with a new design.
Sometimes, with a new feature.
And sometimes, it begins with a decision to rebuild the foundations.
ATLOCK v5.0 is being developed with that third approach in mind.
This isn't the public launch.
This isn't a download announcement.
This is your first look at the engineering direction behind the next generation of ATLOCK.
And yes — there's more happening beneath the surface than a version number change.
🧬 01 — THE CORE IS EVOLVING
ATLOCK v5 introduces a rebuilt cryptographic, storage, and anti-tamper core while retaining the existing interface.
Here's a glimpse of the engineering work:
🔐 Modern authenticated encryption
The current implementation includes:
- AES-256-GCM authenticated encryption.
- Chunked file encryption and decryption.
- Authentication associated with individual chunks.
- Key-commitment verification before plaintext is released.
- Argon2id-based key derivation with HKDF-SHA256 key separation.
The container format has also evolved, with authenticated headers and checks designed to detect modification, truncation, and reordering.
The objective: make the underlying file-protection architecture more carefully structured and resistant to common failure modes.
🛡️ More attention to the things users don't see
Security isn't only about the encryption algorithm.
ATLOCK v5 also includes engineering work around:
- Protected local application state.
- Crash-aware file replacement.
- Verification of encrypted output before replacing the original.
- Recovery mechanisms.
- Windows-specific process and file protections.
These are implementation details, not a claim that every possible attack is defeated.
🧱 02 — REBUILDING THE FOUNDATIONS
A security application has to think beyond the happy path.
What happens when an operation is interrupted?
What if a protected file is modified outside the application?
What if stored data is damaged?
What if a user enters the wrong password?
These questions matter just as much as the main interface.
ATLOCK v5 includes mechanisms intended to handle several of these situations more safely, including authenticated storage, recovery workflows, and verification before committing encrypted file changes.
The goal isn't to make security sound impressive. It's to make the implementation more deliberate.
⚙️ 03 — A GLIMPSE OF WHAT'S INSIDE
Here's a small preview of the current engineering direction.
| Area | ATLOCK v5 development |
|---|---|
| File protection | Chunked AES-256-GCM containers |
| Key derivation | Argon2id + HKDF-SHA256 |
| Data integrity | Authenticated chunks and headers |
| Local state | Encrypted and authenticated storage |
| File operations | Verification and crash-aware replacement |
| Recovery | Recovery keys and one-time recovery codes |
| Authentication | TOTP two-factor authentication support |
| Windows integration | Windows-specific protections and Explorer integration |
| Security monitoring | Defender dashboard, watchdog, and ransomware canary components |
This is a development overview, not a declaration that every component has completed testing or is ready for production.
👀 04 — WHAT ABOUT THE INTERFACE?
Here's something interesting.
The current v5 code retains the existing ATLOCK interface — including its screens, theme, layout, and fonts.
The significant changes are happening underneath.
That means this development phase is focused heavily on the cryptographic, storage, and anti-tamper architecture rather than simply changing the appearance.
Same familiar interface. A different engineering story underneath.
🧪 05 — WHY I'M NOT RUSHING THE RELEASE
Because security software deserves more than a launch-day countdown.
A product can look polished and still contain bugs.
An encryption routine can use a respected algorithm and still be implemented incorrectly.
A feature can work perfectly in one scenario and fail under unexpected conditions.
That's why testing, verification, and reviewing failure cases matter.
ATLOCK v5 is still under development. Its features and implementation may change before a public release.
I won't present it as fully secure, independently audited, or production-ready without the evidence to support those claims.
🔒 06 — ATLOCK v4.0 IS THE PUBLIC RELEASE
While v5 development continues, ATLOCK v4.0 remains the latest publicly available version.
If you want to explore ATLOCK today, you can use the existing release.
📦 Get ATLOCK v4.0
💻 Explore the repository
Please remember: v5 is not publicly released, and the development preview described here should not be treated as a download or upgrade announcement.
💬 07 — YOUR TURN. LET'S TALK.
I don't want this to be just another announcement that people scroll past.
I want to hear from developers, security enthusiasts, Windows users, and people who work with sensitive files.
Here are three questions I'd genuinely like your perspective on:
1️⃣ Encryption architecture
When evaluating a file-security application, how much importance do you place on authenticated encryption, key derivation, and safe file replacement compared with the visible feature set?
2️⃣ Failure handling
What failure scenario do you think developers most often overlook when building file-encryption software?
For example: interrupted operations, damaged containers, recovery workflows, or unexpected application termination?
3️⃣ Your expectations
What would you want to see demonstrated before you would feel comfortable evaluating a new file-security application?
I'm interested in specific technical answers, not just "add more security."
👇 Drop your thoughts in the comments. I want to know what you would examine first.
🚀 THE NEXT CHAPTER IS BEING BUILT.
ATLOCK v5.0 is still in development.
There is more engineering work ahead, more testing to do, and more decisions to make before a public release.
For now, this is a glimpse into the direction.
Not a promise of perfection.
Not a claim that every feature is finished.
Just the next chapter of ATLOCK taking shape.
ATLOCK v5.0
In Development · An Akhouri Systems Product
Built by Akhouri Anmol Kumar
Top comments (0)