Re: Standard for Stenography?
Eli makes a reasonable case for leaving out the length field altogether. The desteg program would produce a file of width*height bits, and it would be up to the next layer to produce text from that. However, I'm not sure it's a *compelling* case. If adding the length doesn't actually hurt security, I'm inclined to keep it.
Tangentially, why choose bit permutation for your second-level encryption? There are plenty of schemes that will be a lot faster than doing all that bitmangling.
Slowness is not necessarily bad - it also makes it harder for attackers to search through large numbers of images for ones with hidden data. But the main thing that the permutation gives you is that it spreads out the data bits among unmodified bits, making statistical tests harder. For a 1000 byte message in a 640x480 image, only 2% of the bits will be changed. If that 2% was all jammed into the first 80000 pixels of the file, it might be detectable; if it's spread evenly throughout the file, it's probably safer. --- Jef
Eli makes a reasonable case for leaving out the length field altogether. The desteg program would produce a file of width*height bits, and it would be up to the next layer to produce text from that. However, I'm not sure it's a *compelling* case.
A steganography program that uses a shared permutation and bit selection schedule on each end is really a symmetric key cipher with data expansion. And because it is a cipher, it is subject to the ITAR. Adding noise intermixed with a signal is a perfectly good way of doing full scale cryptography, it's just that folks these days tend to prefer methods that don't have bandwidth explosion. In fact, bandwidth expansion is only of the few ciphers that has provable information theoretic properties, mostly because the method is simple enough for the basic results of information theory to apply. Hiding encrypted text, which already has high entropy over various word partitions, with an arbitrary embedding in random bits does provably increase the security of the cipher. I would urge Jef to write the code and then submit a Commodities Jurisdiction request to see if the code is exportable. Eric
participants (2)
-
hughes@ah.com -
Jef Poskanzer