4 ms·
OCR doesn't help when you have to find the wrong character in two pages of random stuff. QR codes are your friend.
by stavros 4y ago
OCR doesn't help when you have to find the wrong character in two pages of random stuff. QR codes are your friend.
- mbreese 4y agoI came to say the same. I’ve had long encryptions keys printed out as QR codes and it works surprisingly well. You can still have the text of the key, but the QR code makes it a much easier process. Especially in a situation where you won’t be around to help troubleshoot.
- conductr 4y agoAnd whoever does help has the keys to the kingdom
- mbreese 4y agoWe’re talking about keys and accounts where the credentials (print outs) are stored securely. In my case, it was a safe deposit box. You’d have to expect that whomever is helping to manage that kind of transition is trustworthy. Or at least that the people left behind trust them.
- cperciva 4y agoThat's why the Tarsnap key file format includes a checksum on each line, so tarsnap can tell you which line to look for the OCR (or typing) error on. When I was writing this code I wasn't sure if it would ever matter but figured "hey, why not..." -- but I've probably had a dozen emails since then from users thanking me for including those.
- stavros 4y agoOh nice, I didn't realize it was a custom format.
- cperciva 4y agoIt's base64, but with added checksums, yeah. There's very little that I use off-the-shelf in Tarsnap -- generally speaking I take existing standards and then make tweaks as needed to optimize for Tarsnap's use case. (Sometimes, as with scrypt, I decide that existing standards simply aren't any good and develop my own from the ground up.)