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

Allow user to copy the paper key #239

Open
csbenz opened this issue Mar 3, 2020 · 3 comments
Open

Allow user to copy the paper key #239

csbenz opened this issue Mar 3, 2020 · 3 comments

Comments

@csbenz
Copy link

csbenz commented Mar 3, 2020

I want to copy the Paper Key to 1password but the app doesn't allow copying on the screen. Saving to a password manager is more secure than taking a screenshot which is backed up to the cloud or stays on the local storage.

The whole UX for the key generation is quite bad and doesn't help people onboard to this app. Simple steps can improve it immensely!

@pm47
Copy link
Member

pm47 commented Mar 3, 2020 via email

@t-bast
Copy link
Member

t-bast commented Mar 4, 2020

Saving to a password manager is more secure than taking a screenshot which is backed up to the cloud or stays on the local storage.

Of course if you compare to horrible security measures. It's also safer than posting your seed on Twitter.

But what we currently provide is also more secure than what you suggest. Simply displaying the seed without any other capabilities is the safest we can get without compromising the UX too much. Allowing you to copy means an attacker with access to the clipboard that infected your phone gets your seed very easily. You can't control how long it stays in the clipboard. You can't control where the clipboard stores that data.

On top of that I wouldn't recommend putting your seed in a password manager, unless it's a 100% local (ie offline one). It's of course entirely your choice, but do know that if you do that, you are completely trusting your password manager vendor to not decrypt your seed and steal your bitcoins. You have absolutely no way to protect yourself against that once it has been stored (even encrypted) on their servers.

@t-bast
Copy link
Member

t-bast commented Mar 4, 2020

Before asserting that what we do is bad, please start by asking why it is the way it is. We welcome all contributions, questions and feature requests, and stay humble about what we do, but we expect our users to do the same.

We've put a lot of effort into making this software, making it FOSS, improving it constantly, so the least you could do is have a little bit of consideration for the free work we've done for you.

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

No branches or pull requests

3 participants