-
Notifications
You must be signed in to change notification settings - Fork 24
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
Printer #135
Comments
@BenWestgate solution from Slack:
|
NACK. Maybe look into secure printer drivers? |
One option is to give up on paper copies of the descriptor if we become confident that 14 CD-ROMs are adequate backup. But I'm leaning more towards instructions for L4 that involve buying a new printer and destroying it after use. |
I slightly favor buying a new printer and destroying it after use (and printing it via the a separate computer so as to not have to download drivers on the node). But there's lots of redundancy in the descriptor (inherent in the fact that you only need one). So I wouldn't NACK that |
Reminder that this isn't for any private key data, just descriptors (will show balances/history if recovered/stolen). I'm satisfied with the security of buying a new printer with cash, and then destroying after. Let me know your opinions. |
Instruct users to get a printer that is compatible with Linux?
However, the drivers are
This violates Yeti's security model (possible infection of the online coordinating node). So, perhaps we need to instruct the user to transfer the backup packet to a regular windows/mac laptop to print - this also means it would be easy to print).
Let's discuss.
The text was updated successfully, but these errors were encountered: