5 ms·
Underhanded C: The Leaky Redaction
- ComputerGuru 16y agoThis is the third or fourth time this has appeared on HN this year...
- peterbraden 16y agodo you have links to the other ones - would be useful to see the other comments.
- steveklabnik 16y agoThe only thing I found was http://news.ycombinator.com/item?id=1208097 http://news.ycombinator.com/item?id=1208097
- some1else 16y agoThis reminds me of how some government redacted .doc files by using a virtual "black marker", which of course leaves the text in tact.
- viraptor 16y agoLike in BALCO case? http://www.sfgate.com/c/acrobat/2006/06/22/BALCO_quash_subpoena_sfchronicle.pdf http://www.sfgate.com/c/acrobat/2006/06/22/BALCO_quash_subpo... (page 6, just highlight the text) Or AT&T? http://news.cnet.com/2100-1028_3-6077353.html http://news.cnet.com/2100-1028_3-6077353.html There was also one more subtle source of a leak. some versions of MS Word will try to preserve/serialise the edit history after you save the document. Google filetype:doc and a simple tool were enough: http://lcamtuf.coredump.cx/strikeout/ http://lcamtuf.coredump.cx/strikeout/
- deleted 16y ago[deleted]
- necubi 16y agoIt's a neat idea, but wouldn't work for any image format that's actually used. The code targets PPM, which is an ASCII-based image format. In a binary format like JPG or PNG, different values of zero would be indistinguishable.