I'd like to add an invisible watermark to each PDF document that I produce so that in case it leaks, I know where it leaked from. Anyone knows what would a good way for an invisible watermark be in a PDF document and how to add one?
|
Here a funny idea: Just place some watermark/copyright text on top or below of a dot or other punctuation mark. It is invisible for the naked eye if it uses the same color as the text but can be extracted using copy and paste. You can also give it a dark gray color, so you still have a chance to read it on screen. Here some principal solution:
The dot will then look like this: (note the hard to see text)
|
|||||||||||||
|
|
How about embedding it in an image with steganography, most of the image manipulation libraries such as the GD library have routines available or you can run copies individually and use TikZ!
The message is encrypted in the yellow dots! Some color printers still do it see printer steganography |
|||||||||||
|
|
With the new version (v2.2 - still in CTAN upload process, but should be available soon) of
As soon as you hover over the 0.5cm/0.5cm rectancle in the margin the tooltip pops up. Of course you can put the tooltip in the header/footer or whereever you want. |
||||
|
|
|
If you're looking to track the document itself, it might not be a bad idea to include a serial number or something so that you can track it in printed and photocopied copies... |
|||
|
|
|
Easy way to achieve this, is to intentionally put some carefully placed typos (or punctuation, any sort of slight modification), of no real consequence to the document, prior to issuing it to the respective party, ensuring that you keep a ledger of what changes were made. When the leaked document is identified, cross-reference it with your ledger, then (depending on the nature of your work) call your lawyer and instruct him/her to issue a C&D, or instruct your assets to act accordingly. |
|||
|
|
|
Here is a somewhat academic idea: encode the watermark in the spacing of words or even letters. I don't know a package to support this, though. The obvious benefit is that this encoding survives printing the document before passing it on. Addendum: A variation of this is to individualize a document by tweaking the textwidths of some (or all) paragraphs ever so slightly. That will result in different line breaking and spacing decisions. This would not qualify as an encoding but as long as you know which version was given to whom you would know who leaked a document. I did some experiments that suggest that very small variations to the text width are invisible to the eye but lead to the desired variations of paragraph layout. |
|||||||
|




:-(– Martin May 24 '11 at 22:01