Timeline for Steganography - How many bytes of information can you hide in a $1024 \times 768$ photo?
Current License: CC BY-SA 3.0
18 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 20, 2023 at 2:42 | comment | added | Display name | I'm reading Applied Cryptography by Bruce Schneier and it says "Replace the least significant bit of each byte of the image with the bits of the message. The graphical image won't change appreciably-most graphics standards specify more gradations of color than the human eye can notice-and the message can be stripped out at the receiving end. You can store a 64-kilobyte message in a 1024 x 1024 grey scale picture this way". However, shouldn't an image with this many pixels have a payload capacity of 128KB, assuming a BW pixel is one byte? | |
May 9, 2019 at 0:20 | comment | added | peterh | 1. Encrypt 1024x768x3 bytes. 2. Rename the file as "random_noise.png" | |
Apr 30, 2019 at 19:06 | answer | added | AgapwIesu | timeline score: 1 | |
Jun 5, 2017 at 1:12 | history | tweeted | twitter.com/StackCrypto/status/871535101762555905 | ||
Jun 4, 2017 at 21:33 | comment | added | Paul Uszak | Worse. Chances are the image will be converted to lossy JPEG. Even if the image pixel size remain unchanged, JPEG compression throws away high frequency components (that's the lossy bit). Your compression format will be totally destroyed and the data will be irretrievable :-( You will of course be able to 100% credibly deny there's a hidden message though :-) | |
Jun 4, 2017 at 21:21 | comment | added | bashbin | @PaulUszak Hmm let's say bmp. What will happen to the compressed data if I post the photo on social media? That will get even more compression and the loss of pixels will mean the loss of information, right? | |
Jun 4, 2017 at 21:18 | vote | accept | bashbin | ||
Jun 4, 2017 at 21:18 | vote | accept | bashbin | ||
Jun 4, 2017 at 21:18 | |||||
Jun 4, 2017 at 21:18 | vote | accept | bashbin | ||
Jun 4, 2017 at 21:18 | |||||
Jun 4, 2017 at 21:18 | comment | added | bashbin | @SEJPM sorry mate, it was a mistake on the lectures and I thought this was more complicated thats why I posted the question here. Yes, you're correct! | |
Jun 4, 2017 at 3:01 | answer | added | Paul Uszak | timeline score: 9 | |
S Jun 4, 2017 at 1:16 | history | suggested | user47922 | CC BY-SA 3.0 |
texify, fixed weird use of "in maximum"
|
Jun 3, 2017 at 23:33 | review | Suggested edits | |||
S Jun 4, 2017 at 1:16 | |||||
Jun 3, 2017 at 20:47 | comment | added | Paul Uszak | @SEJPM Well, actually a lot more if the data is compressed. You'd probably get ~5Mbits if it's text like love letters etc. | |
Jun 3, 2017 at 18:18 | comment | added | SEJPM | Uhm, maybe $1024\cdot 768\cdot 3\cdot 1=2359296$ bit? | |
Jun 3, 2017 at 17:21 | answer | added | Meir Maor | timeline score: 3 | |
Jun 3, 2017 at 15:17 | review | First posts | |||
Jun 3, 2017 at 23:33 | |||||
Jun 3, 2017 at 15:15 | history | asked | bashbin | CC BY-SA 3.0 |