-
Notifications
You must be signed in to change notification settings - Fork 13
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
Password Protect Wasabiwallet #39
Comments
Idea ACK. I was surprised we didn't have an issue already opened for this. I added it to the technical plans document to the "Extending the Scope of Privacy" section. |
We already discussed this a couple of times with different level of analysis and last time we agreed that someone with physical access can do many things, it could simple open and view the wallet file, sent it to himself, install malware and similar actions. "Protect" the UI with a password can improve the feeling of security/privacy but that will not be something real, just an illusion. |
I do think that it is important to understand what this password is useful for. If you just think about protecting your wallet balance/history from been seen by anybody with a few min access to your laptop than it is of course valuable. Because nobody with short time access to your machine can just open wasabi wallet and check balance, history, transaction IDs. So password would not protect from a state actor who has seized your machine and has months/years to work on it. |
It's duplicate btw: #36 |
We did:) |
Yes, agreed with @btcpirate, we should do everything possible to defend against all levels of attacker. Yes, there is not a perfect fix for defending against super adversaries, but this already solves many issues in context for low-level attackers. |
This is solved by WalletWasabi/WalletWasabi#1681. I am closing this. |
"solved" is an ambitious word 😄 |
Rephrasing:
P.S.: The lock screen is truly just for locking the screen of the wallet. With some "hacking" in the UiConfig, the lock screen can be turned off. |
Can we please re-open the issue? An interesting consideration is how this would work with the upcoming multi wallet support. A wallet is only loaded after the password is typed in? From a UI point of view, I would have it like the |
Encryption is doable. On the other hand, if the goal is to prevent malware-like activity you must know that accessing Wasabi's memory (with a debugger) is not a big deal. |
As of now everybody opening the machine wasabi is running on can see transaction history (coin join history) of all wallets.
The easiest way (UX related) to password protect the whole wallet would be to offer a checkbox when setting up the wallet password that says "encrypt wallet" so if a user ticks the box he will be asked at every launch of wasabi to enter this password to gain access and prevent unauthorised users to open the wallet, check the balance, see the history, etc...
The text was updated successfully, but these errors were encountered: