Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I don't think it's quite that simple. There are all sorts of small things people can miss during document forging: leaking of metadata (not stripping a PDF), leaking of IPs, bad forging (a notable example is the "Killian documents", purportedly from 1973 but which were probably made with Microsoft Word[0]).

Distribution/guiding matters too, especially on the internet: what's the best way to place it so it will spread? What techniques will be caught? Should you run a botnet? How difficult is it to evade detection? Light touch or heavy handed? Do you need a base of fake accounts years in advance, or can you create them at the time?

Red team/blue team exercises are valuable for defense. If you "practice" only by examining real-world propaganda, you can't debrief the opposition at the end. And if you can't debrief the attacker, you can't find out what you missed and what would have been effective.

[0]: https://en.wikipedia.org/wiki/Killian_documents_controversy



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: