News for hackers. Stuff that matters.
Re:Identifying HTTPS-Protected Netflix Videos in Real Time [... by notgood on Sunday April 09, 2017 @03:02AM (#14070878)
> Even with CBR, the exact length of the video might give away the contents too.

To avoid that issue you just artificially make multiple movies have the same length, meaning do some padding to round up to the next e.g. 10 minutes (so if the movie is 1:48:23 it becomes 1:50:00), to do so the movie keeps buffering in the background (some random audiovisual noise).

Maybe netflix should have a "Fully safe" mode where it uses CBR instead of VBR so the user knows the trade off (slower/heavier buffering)

Re:Identifying HTTPS-Protected Netflix Videos in Real Time [... by Franciscouzo on Sunday April 09, 2017 @10:58AM (#14072581)
It wouldn't work, that sounds like adding sleep calls to prevent timing attacks, which doesn't works...

Different bit rates on the random audiovisual noise (white noise would be uncompress-able, thus weight more, pure black would be too compress-able, etc).

Re:Identifying HTTPS-Protected Netflix Videos in Real Time [... by aianus on Sunday April 09, 2017 @11:46PM (#14075843)
Why wouldn't adding sleep calls help prevent timing attacks? Assuming you're padding all response times to the same total response time.