Timeline for Pad ciphertext with arbitrary number of bits
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 3, 2017 at 1:05 | comment | added | Paul Uszak | Your dilution is exactly how it's done. I don't have references, but I've read about it being done by encoding < 1 bit /pixel/channel. | |
| Nov 2, 2017 at 22:41 | comment | added | Fax | @PaulUszak Good point. I imagine that a photographic RAW file is pretty close to random LSB, but that does limit application a lot. Perhaps I could dilute the ciphertext across the image instead of padding it? | |
| Nov 2, 2017 at 3:03 | comment | added | Paul Uszak | A small flaw: ciphertext is 100% uniformly distributed. It's perfectly pseudo-random. The lsb of a natural photograph isn't at all. This will also be a dead giveaway to anyone looking for a message. And TIFF, PNG, BMP and GIF photographs are also suspicious as they should be JPEGs really. | |
| Nov 2, 2017 at 2:39 | vote | accept | Fax | ||
| Nov 2, 2017 at 2:39 | comment | added | Fax | @PaulUszak In this case I'm encoding the message in the LSBs of an image. If the seemingly random bits were to suddenly stop partway though the image, it would be a dead giveaway that a secret message is present. | |
| Nov 1, 2017 at 2:25 | comment | added | Paul Uszak | What is the (atypical) purpose of padding the message? | |
| Oct 31, 2017 at 22:24 | answer | added | Fax | timeline score: 0 | |
| Oct 31, 2017 at 8:16 | comment | added | daniel | I like OAEP and the papers about it, others will say don't roll your own. | |
| Oct 31, 2017 at 0:55 | review | First posts | |||
| Oct 31, 2017 at 3:08 | |||||
| Oct 31, 2017 at 0:52 | history | asked | Fax | CC BY-SA 3.0 |