Earlier quoted context omitted.
I completely understand — building trust is key, and we’re working on adding transparency through decentralization and exploring open-sourcing to give users more control over their data.
How will you prove the decentralization is real and not some BS written by a scammer? How will you prove your app matches the open source to someone that can’t compile it themselves?
Show HN: End-to-End Encrypted Dead Man's Switch
51–56 of 56 posts
Re: Show HN: End-to-End Encrypted Dead Man's Switch
#52PSA: Looking over their replies to the comments here, benefit of doubt is vanished. I'd urge everyone to be very wary.
Re: Show HN: End-to-End Encrypted Dead Man's Switch
#53Earlier quoted context omitted.
What exactly is preventing someone with the key decrypting the data before some other code in your system runs?
Only the people who you've added in your beneficiaries can decrypt the data if Cipherwill is hacked.
Re: Show HN: End-to-End Encrypted Dead Man's Switch
#54Re: Show HN: End-to-End Encrypted Dead Man's Switch
#55Earlier quoted context omitted.
This is basically saying "trust us" and does not instill confidence in your system.
will definitely fix this
I'm sure the product has potential, and lots of effort has gone into it. I also see that criticism is hard, but if you can't be open about these basic questions then there are fundamental problems.
I should say, I'm a fan of crypto' (both types) and i'm likely your target market because currently my plans after death are not nearly as secure as i'd like!
Re: Show HN: End-to-End Encrypted Dead Man's Switch
#56Earlier quoted context omitted.
Thanks for your feedback! Here’s a quick response to your concerns: 1. Private Key Storage: Private keys are derived locally from your security factors when you set up them. 2. Time Capsule Keys: The release of "time capsule" keys is governed by strict protocols, ensuring they’re only accessible at the specified time. 3. AES Encryption: We use AES-256, not 512, will fix that typo. 4. End-to-End Encryption: yes, End-t…
Thanks for responding! What are these "security factors" you keep mentioning? It's a vague term and I don't see a definition on your website. Can you also describe how private keys are derived from them? That's what I'm most curious about. Is this derivation process something that could be replicated by an attacker?