Good luck
Nice effort, but looong loong way from success.
We implemented proprietary security mechanisms (using standard aes256 of course) and thus we do not provide any shortcuts.
Sole purpose of any crypto wallet is to NOT MAKE IT EASY to even try to approach brute forcing….latest example of this is Ledger users receiving FAKE LEDGERS with changed software etc..sad but true. Open source is two edge sword and one edge is hackers exploiting it.
I wish you luck with trying the passwords.
Thanks for replying!
This thing is becoming interesting to me, because if i am not successful, my funds will be locked forever, so, no chance to fail here.
I think that you are right for looking for security in your device, this is the thing we want when we look for hardware wallets. But, i also think that open source is not the problem. The real question on open sourcing things is the way you do it. There are a lot of open source and secure things, like bitcoin itself, linux, and so much on. The problem is how you deal with people involved with your business. Wouldn't be great if we, the community, help you make BCVault even more secure then it is? Someone, maybe not me, WILL sooner or later decrypt the file, or hack the device. I just think that BCVault should be involved on this in a responsible and secure disclosure, not to get caught by surprise.
It is a great start to us to hear from you that this is an AES-256 secured device, but also, you mention you implemented security mechanisms. Which of the seven AES operation modes did you used? ECB, CBC, CTR, PCBC, CFB, OFB or GCM? How the password and PIN are hashed to form the key, is it an known hashing function?
Hope you get involved and hear to us, your actual, and possible clients.
