Secure Vault encrypts your files with AES-256-GCM β but instead of protecting the key with a password, it lives on a USB drive you register as your master key. No password to lose, phish, or leak. Plug the drive in to decrypt, unplug it and your files are locked. Free, open-source, built for Windows. One-click installer, encrypted local backups, and optional email alerts on vault activity.
No reviews yetBe the first to leave a review for secure vault .exe
Maker
π
Hey Product Hunt π
Maker here. I built Secure Vault because I wanted a way to encrypt
sensitive files without relying on a password as the only line of
defense β passwords get phished, guessed, or leaked, but a physical
USB key can't be stolen remotely.
How it works: register a USB drive as your "master key," and it has
to be physically plugged in to decrypt anything encrypted with it.
The obvious tradeoff β lose that drive with no backup, and there's no
password reset β is intentional, and I've tried to be upfront about
it rather than bury it in fine print.
It's fully open-source if you want to check the crypto implementation
yourself before trusting it with anything real: [GitHub link]
Would love feedback, especially from anyone who wants to poke holes
in the security model β that's more valuable to me than upvotes.
Report
The USB as physical key is a really elegant way to sidestep password fatigue and phishing entirely. Love that the source is open too, makes it way easier to actually trust what's running on my machine.
The USB as physical key is a really elegant way to sidestep password fatigue and phishing entirely. Love that the source is open too, makes it way easier to actually trust what's running on my machine.
@lyas1079320Β Thanks, really appreciate that! π
That was exactly the goal - passwords are the weak link in most
"secure" tools because they can be phished or leaked without you
knowing, but a physical key can't be stolen remotely. The tradeoff is
real too (lose the drive with no backup and there's no recovery), but
I'd rather be upfront about that than pretend it doesn't exist.
And yeah, open source was non-negotiable for me on this one - an
encryption tool asking for blind trust felt backwards. A community
member actually did a deep code review recently and found some real
issues (weak-ish memory handling, a command injection edge case) - all
fixed now in v3.3.0, written up in the changelog. That kind of
scrutiny is genuinely the best thing that can happen to a project like
this, so if you ever want to poke at the code yourself, I'd take it
seriously.
Let me know if you end up trying it out - curious how the USB
registration flow feels for a first-time user.