3 ms·
This has nothing to do with compression. If you use "yes" and "no" instead of "oui" and "non" (which just happen to be three characters each) and you compress
by lisper 3y ago
This has nothing to do with compression. If you use "yes" and "no" instead of "oui" and "non" (which just happen to be three characters each) and you compress "yes" to "T" and "no" to "F" then the uncompressed text will be the leaky one.
- stouset 3y agoIt’s an example meant to prove the idea.
- lisper 3y agoYes, and my example was an example meant to prove the opposite idea. The point is that it is irrelevant whether you compress or not. You can leak information either way.
- iraqmtpizza 3y agoI leak the length of my phone call and you leak: 1. the length of your phone call; and 2. what language you were speaking; oh and 3. half the words you said (i.e. pwned) https://web.archive.org/web/20080901185111/https://technology.newscientist.com/channel/tech/dn14124-compressed-web-phone-calls-are-easy-to-bug.html https://web.archive.org/web/20080901185111/https://technolog...
- lisper 3y ago> you leak [a bunch of stuff] How? Remember, the uncompressed text gets encrypted too.
- iraqmtpizza 3y agoIt's in the article if you would bother to read it LOL. "simply measuring the size of packets without decoding them can identify whole words and phrases with a high rate of accuracy . . . [the researchers] can search for chosen phrases within the encrypted data"
- lisper 3y agoAh. That article is about voice calls. Totally different topic. Nothing to do with UTF-8.
- iraqmtpizza 3y ago[flagged]