ATLOCK v5: 13-Year-Old Developer Builds Security Suite
A 13-year-old developer builds ATLOCK v5 on an HP 240 G9 laptop, advancing Windows security architecture with Argon2id and AES-256-GCM.
Stock photo for illustration only, not from the actual event
- A 13-year-old developer built ATLOCK v5 using a single HP 240 G9 laptop
- Upgrades security architecture with Argon2id and chunked AES-256-GCM
- Adds support for FIDO2, Windows Hello, and TPM-backed Windows CNG keys
- Current public release is v4 while v5 remains under active development
No funding, no team, no mentor, and no enterprise lab. Just a 13-year-old developer, an HP 240 G9 laptop, and a security project that continues to expand. While ATLOCK v5 is still under development and has not yet been publicly released, users can download and test the current public release, ATLOCK v4, via GitHub.
The major shift in v5 moves ATLOCK from a basic file-locking application into a serious Windows security architecture. While v4 utilized File Guard via Windows NTFS ACLs and a vault based on Fernet with PBKDF2-HMAC-SHA256, v5 completely redesigns the underlying security core to handle advanced cryptographic demands.
The fact that a 13-year-old can develop such a comprehensive security architecture using just a single laptop highlights how accessible modern software development tools have become. Although lacking a specialized hardware laboratory, deep dedication and self-directed study made implementing advanced encryption standards possible.
The core technical upgrade in ATLOCK v5 centers on a file container built around chunked AES-256-GCM. Data is processed in authenticated chunks, with independent authentication for each segment and the container header. Container v3 specifically incorporates independent per-chunk authentication, key commitment, and authenticated header handling.
For credential management, v5 utilizes Argon2id as a memory-hard password-derived key foundation, passing through HKDF-SHA256 for domain separation. Instead of relying on a single key for everything, v5 separates cryptographic purposes across distinct domains such as file keys, vault keys, audit keys, and session protection. It also includes a built-in self-test suite to verify container integrity and tamper detection.
"Let's make another password-protected folder."
Developer
Source: Dev.to
Found something wrong in this article? Report an issue with this article
Comments
Leave a Comment