Step 9 is impractical.
If your box is owned already, what's to stop malware from stashing the keys somewhere, waiting for you to reconnect?
Step 9 ("Make sure the private keys are not saved anywhere on the computer") means not to purposefully keep such copies. If there's a virus that stores them and reads on reconnecting there's not much to do in this setup. But if the computer is clean and later gets infected, not keeping keys protects you (otherwise it's not a paper wallet).
Good job!
Thanks.
Pretty photos of each stage wouldn't go amiss, people like those!
Lots more work but I'll keep in mind.
Secondly links to download ubuntu or whatever you're recommending to install on a USB to get this set up with so people can just click, click, click to get up and running.
Ubuntu is classified in this guide as "extra credit", people who want to do this need a guide for this in particular.
Only took a quick scan but also make sure that people write down their private key at least twice, probably three times. letters like i and l look very similar.
Private keys are Base58-encoded, so I and l don't exist. But yes, it is recommended to keep multiple copies, and if printed, use a clear font.
- Mandatory: Live CD reboot your real hardware (no virtual machines)
- Get the address.org.html from github:
https://raw.github.com/pointbiz/bitaddress.org/master/bitaddress.org.html- Verify file checksum,
- Single address at a time per paper wallet and entropy set,
- All that is needed is an address + wif privkey (bitaddress.org gets this wrong with too much info), choose compressed addresses,
- Print and preserve the wallet like they were $10000 bills, but ones that can have backups.
What's mandatory is that people will actually do this rather than give up on the whole thing and keep their funds in an even worse-secured wallet (which they will if you burden them with all of these).
I thought I'd point out that on your site in general, the cross site requests are blocked by requestpolicy, and one of your css filenames catches default adblock rules, making it look like this:
I don't really know what this means. I'm using wordpress.com's hosted platform (paid for most features with Bitcoin) and was hoping they would take care of such things for me... If you have an idea what can be configured to solve this I'll be happy to hear.
My site with no off-site requests, I could host a blog page here for you, but would probably write my own uber-paranoid version of "paper wallet":
Not much point in having you host this, of course if you're up to writing a guide for a more secure paper wallet it would be great.
Show Posts
