Skip to content
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

Closed
ligi opened this issue Oct 31, 2018 · 12 comments · Fixed by #87
Closed

Plausible deniability #7

ligi opened this issue Oct 31, 2018 · 12 comments · Fixed by #87
Assignees

Comments

@ligi
Copy link

ligi commented Oct 31, 2018

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.

@bitgamma
Copy link
Contributor

Will do, I am back from Prague and I am organizing all the discussed items to start working on them.

@bitgamma bitgamma self-assigned this Oct 31, 2018
@cryptoida
Copy link

Did you decide to implement a plausible deniability option?

@bitgamma
Copy link
Contributor

bitgamma commented Mar 4, 2019

we are now focusing on other aspects, but in the future it will come

@cryptoida
Copy link

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 :)

@cryptoida
Copy link

Hello,
Haven't implemented this plausible deniability option yet?
Thank you !

@guylouis
Copy link
Contributor

We have not yet, indeed, since it's been on the lower priority list, especially compared to enabling payment scenarios in keycard.
However, this is interesting, could you elaborate on the use case you'd have with a keycard that implements a plausible deniability feature ?

@cryptoida
Copy link

Personally, I can't imagine a hardware wallet, without the implementation of plausible deniability.
This functionality should BE indispensable, but not only optional.
There are multiple reasons: protection against any form of constraint :oversight, government constraint, hacking, blackmail)

@willianpaixao
Copy link

Hello, @guylouis @bitgamma maybe we could try to get this done? I can help.

@bitgamma
Copy link
Contributor

bitgamma commented Dec 2, 2022

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.

@willianpaixao
Copy link

cc @ligi @gballet for visibility.

@ligi
Copy link
Author

ligi commented Dec 3, 2022

Really nice - will you cut a release with this feature?

@bitgamma
Copy link
Contributor

bitgamma commented Dec 4, 2022

sure, we will cut a release soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants