31–40 of 46 posts
Be careful where you print these. Most full-featured printer/copier/scanner devices found in office environments can store print job data on the HD where service technicians can access it.
Be careful where you print these. Most full-featured printer/copier/scanner devices found in office environments can store print job data on the HD where service technicians can access it.
The usage guide shows which command to run to generate a QR code from a file, and outputs a PDF. But then the command for recovering a file from QR codes takes "file.txt" as input. Is that a typo? Shouldn't that input also be a PDF?
Earlier quoted context omitted.
You're posing a good question but, if you look at things from this perspective, then every time you type the password to decrypt your private key you should worry about the possibility of some software running on your machine reading it and sending it somewhere. While you pose a valid concern, I think most people don't have to worry about this. The reason is that printing private keys isn't a common practice, so I th…
This certainly applies to office printers. Printers that accept new jobs while printing have to store them somewhere. There have been many incidents of finding old documents on disposed printers because it doesn’t occur to anyone to wipe them first. This especially applies to “copiers”, because a copier is just a printer in the same box as a scanner.
Be careful where you print these. Most full-featured printer/copier/scanner devices found in office environments can store print job data on the HD where service technicians can access it.
[0]: https://github.com/matiaskorhonen/paper-age
Edit: I now see it was already mentioned.
I keep meaning to do something like this in combination with Shamir’s secret sharing (which allows you to split a secret into M blocks, of which any N can be combined to recover the key, and M and N are configurable) to distribute a private key among family members in case of my untimely demise so they can more easily access my financial accounts and stuff. Has anyone done that before, and if so, what tools do you pr…
How safe is printing a private key, considering potential vulnerabilities in the printer software, firmware, and its online connectivity?
You're posing a good question but, if you look at things from this perspective, then every time you type the password to decrypt your private key you should worry about the possibility of some software running on your machine reading it and sending it somewhere. While you pose a valid concern, I think most people don't have to worry about this. The reason is that printing private keys isn't a common practice, so I th…
Yes, I believe you should. On OSes without sandboxing and protections against exfiltration, this is a substantial concern. And you’d be foolish to e.g. keep a bitcoin private key lying around in your home dir. For this same reason, I think the common practice of leaving non-password-protected SSH keys in ~/.ssh is terrible.
I keep meaning to do something like this in combination with Shamir’s secret sharing (which allows you to split a secret into M blocks, of which any N can be combined to recover the key, and M and N are configurable) to distribute a private key among family members in case of my untimely demise so they can more easily access my financial accounts and stuff. Has anyone done that before, and if so, what tools do you pr…