Comments for Digital Invisible Ink Toolkit
Sparse doc.
Hi,
it might be useful if you wrote - how many bytes it can code (probably fraction of height x width, 1/100?), examples of hidden information with different sizes etc. There is also certainly a way to decrypt it, which is not mentioned at all. Comparison with other similar tools would be interesting as well....
jaromrax
Re: Sparse doc.
> Hi,
> it might be useful if you wrote - how
> many bytes it can code (probably
> fraction of height x width, 1/100?),
> examples of hidden information with
> different sizes etc. There is also
> certainly a way to decrypt it, which is
> not mentioned at all. Comparison with
> other similar tools would be interesting
> as well....
> jaromrax
I agree - I'm currently working on all the documentation, and will post it up to the homepage as soon as it's done. As a quick answer though:
The number of bytes it can encode is maximumsize = (imageheight * imagewidth * 3 * (endbits - startbits)) / 8
Which is the size of the image, times the number of colour values (red, green, blue) times the number of bits you define to hide it in. I think I have allowed a maximum of 7 bits to hide in. It's divided by 8 to turn bits into bytes.
The tool decrypts the hidden message too - as long as you know the algorithm it is hidden using and the password. The only other way to decrypt the hidden message is to try every combination of passwords - which takes a very long time as it's hidden randomly.
From what I've seen of other lsb steganography tools, this performs a lot better, almost halving the detection rate. As part of the final release there will be a load of benchmarking put into the interface, so you are able to see for yourself how well the different algorithms do.
I will work on the documentation but the next release is sure to be a lot better.
Thanks for the feedback :)
Kathryn