Description: "ATLOCK v5 by Akhouri Systems: Argon2id + AES-256-GCM encryption, a decoy vault, FIDO2, ransomware canaries, Shamir recovery, and a se...
For further actions, you may consider blocking this person and/or reporting abuse
@effessdev how much will you rate it?
Let me evaluate it first... 🤔 I will give the rating soon!
okay waiting for the rating ⏳
This makes me remember my File Encrypter! Honestly, I still couldn't understand what exactly it is really. But from the first impressions, I'd say it sounds really good, maybe a 9 or something? Let me actually try it in my PC. Now I am in bus, unfortunately :( But I will try it when i reach home! I starred the repo too!
thanks for starring the repo bro
and yeah when you will be at home try it.
bro but still you don't understand about what it is lol.
no problem when you will try it you will understand it.
it is " Total Security Suite"
like you said your file encrypter, it is also a security tool but the difference is that yours one or any security tool in market may be one file encrypter, 1 password manager or else.
but it combines all in one suite.
also it has excellent cryptography, 80% file locking apps just hide the files, 10% locks them actually but weak cryptography while ATLOCK falls in best 10% with excellect cryptography.
when you will try it you will for sure understand it and may make ATLOCK your default security tool installed in your PC. like I've 👇
This is seriously ambitious 😸
There’s a lot here that I really like, especially the fact that you clearly wrote down the limitations instead of trying to make the security sound perfect. The KDF limits, authenticated encryption, rollback protection, recovery options, and panic mode all show that you’ve put a lot of thought into the design.
Just from the architecture and documentation, I’d probably give it around 8/10.
That said, I haven’t installed the executable, so I don’t think it would be fair for me to rate the actual security of ATLOCK yet.
For something security-related, I’d personally want to look through the security-critical implementation first, especially things like key handling, nonce generation, container parsing, rollback protection, and the FIDO2 flow.
Right now I can see the documentation and the release build, but not enough of the source to properly verify those parts myself.
Project / design / ambition: 8/10
Actual security: not rated yet
Either way, you’ve clearly put a huge amount of work into this. Keep going! 😸
bro download it & try.
because I'm heard that ATLOCK's UI is not good can you try it?
in full maximize window.
try it bro please only UI part I want to know.
Yeah bro, I totally get you 😸
I’d love to help with the UI feedback. I’m just a little careful about running unsigned security tools on my main Windows machine. I work in an enterprise environment, and with all the security incidents lately, I’ve gotten pretty cautious about what I run locally.
So it’s really just me being careful 😅
If you send me a few screenshots in a fully maximized window, or even a short screen recording, I can still give you proper feedback on the layout, spacing, readability, and overall UI.
Happy to take a look, bro!
in discord?
Totally get it! 😅 I also didn't want to run it... This is a problem with almost everything open source that's built by a single dev, unfortunately :(
but still you downloaded it thanks for the trust.
@xulingfeng what's your rating?
I’d rate it 7/10. Docked 3 points because there’s only a Windows build, no macOS version.🤣
due to it will lost many features if I port it to macOS too.
bro but you are rich rich, just buy a windows(you have right in your setup I remember) and use it if you want(you denied to use it)
True, I have a Windows PC! Still, cross-platform support would open this tool up to way more users 😄
oh sorry I thought just you are having issue lol.
my mind is lagging now.
and yeah you are right even I thought in between developing ATLOCK v5 but skipped it due to some lazy reasons maybe 🔥
but for v6(if it came) then you will see cross platform support for sure.
bro I launched v5 just today and seeing about v6 plan is like good but my mind is shouting from inside my mind is saying: anmol bro, you just released v5 after killing me and now planning about v6 bruhh I'm out lol.
Fast is slow, slow is fast. Take this to heart, hahaha😆
bro I am guessing you've forgotten something....
mustafa bro Isn't?
🤣🤣🤣
bruhh.
Hey Anmol! 😄🔥
You really don’t make it easy to keep up with you, do you? 😂
I took some time to examine the ATLOCK v5 package, including its executable structure, documentation, and security architecture.
My rating: 8/10 for the engineering approach. 👏
What impressed me most wasn’t the 10,000 lines of code or the number of features. It was your attention to threat modeling, versioned encryption formats, KDF resource limits, recovery mechanisms, and especially your willingness to document security limitations.
A few things I’d encourage you to investigate further:
These are questions worth testing, not confirmed vulnerabilities.
I also appreciate that you included fuzzing and self-tests. That’s a great direction, but independent verification is what will really take ATLOCK to the next level.
My suggestion for v6? Don’t rush to add more features. Focus on proving that the security mechanisms you’ve already built actually hold up under adversarial testing.
And one more thing: I wouldn’t deduct points simply because you used Python. Security depends much more on implementation, architecture, and threat modeling than the programming language itself.
I haven’t completed a source-level audit or dynamic security assessment, so my 8/10 reflects the design and engineering effort, not a certification of its security.
Keep going, my friend. You’re building something ambitious, and I’m genuinely curious to see how far you take it. 🚀
And please, get some rest before v6. You’re making the rest of us look lazy! 😂👏
Brooo, you said you will break it... bro try to break
also thanks for your kind words. (bro what I done? to make you guys look lazy lol you guys have job, I've no job I'm kindaa unemployed lol for now just for name I'm Founder & CEO but with 0 revenue or PAT.
btw, Temporary plaintext: opened files live in a protected working folder, and a leftover-recovery routine tries to wipe anyything a crash left behind at the next start. But a crash can still leave a plaintext copy until then, and I can't guarantee deletion on SSDs. I need to test the crash cases properly I thought I'm done lol. let me test it...
Anti-rollback: this is myyy weakesttttt spot. A same-user attacker who can restore the encrypted state together with its anchors Could probably reset a counter. The design makes that harder, but I've never claimed it's impossible.
Chunked AES-GCM: each chunk's authenticated data includes the header hash, chunk index and a final-chunk flag,, and each file has its own subkey and key comittment, so reordering, dropping, Duplicating or truncating chunks and swapping chunks between files should all fail. "Should" is the key word, so this is exactly what I want people to try to break.
FIDO2: it depends on the feature. In File Guard's extra lock the key's hmac-secret becomes part of the encryption key, so it's Crypto graphically involved. For login 2FA it's only a gate, and that's written in the code.
nd for code signing and audit I need money 💵 which I don't because I dont have funding, support, so yeah I can't do so for now....
v6 will be more great as you can see the jump from v4 to v5 was massive I will try more bigger jump next time from v5 to v6 with your feedbacks implemented too.
I'm not like a fruit brand who always change or introduce new color and market it as a latest beat mobile( no apple was harmed lol) and not like samsung too literally no clear difference between S25 ultra and S26 ultra lol.
I literally re structured v4 to v5 completely.
And thanks for the 8/10, I know that's for the design and not a security certification. bro but break it and give final rating too.
I worked harder just because of you broooo....
Brooo, you actually came back with technical answers to every single point. Now THAT is what I like to see! 😂🔥
Your explanation of the chunk authentication and FIDO2 hmac-secret integration is particularly interesting. Those are meaningful design decisions, not just features added to a checklist.
And I respect your honesty about anti-rollback. Knowing where your security boundaries end is just as important as knowing where they begin.
About the money: don’t worry about commercial code signing or paid audits right now. You can still make serious progress with reproducible tests, published test vectors, fuzzing, and community code reviews.
As for breaking ATLOCK, challenge accepted. 😎 But I won’t call something a vulnerability until I can reproduce it, and I won’t give you a final security rating without evidence.
One condition, though: no v6 feature explosion until we’ve properly tested v5! 😂
And bro, you don’t need revenue or a CEO title to prove you’re a developer. Your work speaks for itself.
Now get some sleep. Your brain deserves a maintenance window. 🤣👏
deal done.
thanks my CTO lol.
@technogamerz
@xulingfeng
@koda2026
@nyaomaru
Mustafa ERBAY
rate ATLOCK v5 in a scale of 10.
Please 🙏
my rating for ATLOCK_v5: 9.7/10 🔥🖐️🤚☠️
-0.3% because of python limitations.
akhouri, my brother and CTO! 🐯🤝
seeing you ship a 10,000-line security suite at 13 is exactly the kind of elite, constraint-driven engineering I expect from my co-founder. i rate the ambition and execution a solid 10/10, no hesitation.
those python limitations are just temporary roadblocks; our vision and execution are permanent. proud to be building alongside you. let's keep securing the perimeter and shipping! 🔥🛡️
thanks.....
KODA-AI nd ATLOCK our 2 flagships
different mask, same task 🎭
LEGENDARY ❤🔥