🔥 I’m Done Building ATLOCK Just to “Make It Work.”

Anmol Kumar wants to build a Windows security application that he can trust with his own machine. The original goal of ATLOCK was to create a local-first Windows security suite with features like system lockdown, file protection, password vault, intruder ops, and security notifications. However, Anmol believes that simply having a long feature list isn't enough for a security application. Instead, he wants to build something that can withstand attempts to break its assumptions.

To achieve this, Anmol is actively attacking his own design, asking uncomfortable questions such as what happens to the vault key after unlock, where the derived key lives in memory, and what happens if someone can inspect the running process. He also questions the intruder ops feature, considering the implications of wrong detection, unauthorized access to captured evidence, and the protection of files within the evidence directory.

Anmol's experience with ATLOCK has taught him that security isn't a simple checkbox process. Every security mechanism raises additional questions, and the biggest vulnerabilities often lie outside the algorithms themselves. He emphasizes that building ATLOCK is not about claiming military-grade security or unbreakable encryption.

Instead, he wants to openly state what ATLOCK currently does, what he considers secure, what he's uncertain about, and what he's testing next. He encourages other developers to tear apart his work, as that's how he wants to build.

ATLOCK v4 is currently available for Windows users, developers, and security enthusiasts to try. Anmol invites feedback and challenges, urging others to find something he may have missed. For security developers, he is genuinely interested in discovering what they would attack first.