>Moreover the chaff volume could be expanded exponentially for a given track >by the person using that track for stego cover. In addition to the version >"loaded" with stego data, it would be simple to make subtle bit >modifications to a hundred or a thousand different "unloaded" copies of the >same track and insert them all into the system, where they will spread if >audio quality is not unduly compromised. A better solution would be a hi-fi freeware mp3 encoder that would make (almost) truly random choices when encoding (mike input, file system specifics*). Tons of chaff. * It just occurred to me that a trojan mp3 encoder could put anything (like user ID, and anything from user disks) into an mp3. Broadcasting data with non-trivial structure (that cannot be manually inspected) is inherently dangerous. Which is the basic problem: your security wrt crypto is proportional to your understanding and investment in the support. I wonder if crypto insensitive to trojan attacks and user stupidity can be designed - maybe in silicon ?
