-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plausible deniability #7
Comments
Will do, I am back from Prague and I am organizing all the discussed items to start working on them. |
Did you decide to implement a plausible deniability option? |
we are now focusing on other aspects, but in the future it will come |
This functionality is indispensable and for some clients like me it would be the only reason why I would not adopt the keycard project ....I hope to be integrated soon :) |
Hello, |
We have not yet, indeed, since it's been on the lower priority list, especially compared to enabling payment scenarios in keycard. |
Personally, I can't imagine a hardware wallet, without the implementation of plausible deniability. |
finally implemented card-side, will need proper wallet support. i.e. the wallet app should not reveal the public key/address in any way before authentication and be ready that an "unexpected" public key will be used, otherwise an attacker could easily verify that the address does not match if they are using the card holder's mobile to check. |
Really nice - will you cut a release with this feature? |
sure, we will cut a release soon |
as talked about the magicians gathering after cryptolife: It would be great to be able to specify N>=1 PINs to lead to different derivation paths to gain plausible deniability.
The text was updated successfully, but these errors were encountered: