3 ms·
My vote for encoding a key in a document goes as follows: Make 3 spelling errors. Anywhere. Copying all the text from my AgileW/Rails book comes out to 13920
by Groxx 16y ago
My vote for encoding a key in a document goes as follows:
Make 3 spelling errors. Anywhere.
Copying all the text from my AgileW/Rails book comes out to 1392025 characters (wc -c). Comes out to being able to make 2,697,367,802,211,997,800 unique copies by location alone[1]. Significantly less data than a SHA key, but far more than necessary. Heck, making two unique errors gives you almost 2 trillion unique copies. Most books have a fair amount of errors already, what's a couple intentional ones? And note that it can be hidden in metadata too, so there's even more room.
[1]: (1392025 * 1392024 * 1392023)
- donaldc 16y agoSpelling mistakes are better than nothing, but if I can obtain two copies of the document, I can diff them and fix the mistakes.
- eli 16y agoI could diff a dump of all the kerning values too.
- Groxx 16y agoI picked spelling specifically because copying / OCRing will destroy kerning values, but not (likely) spelling. And if you change words into other words, running a spell check might not clean them out either :) But yes. Diffing is always an option, and it's an ideal way to reveal steganographic data if you encode more than one thing in the same document.