From: Sebastian Moeller <moeller0@gmx.de>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Using buffer filling as (sort of) side channel that leaks information
Date: Wed, 26 Jun 2024 11:51:37 +0200 [thread overview]
Message-ID: <ED1986B6-B9E6-4569-8C9A-6E91F9308CDD@gmx.de> (raw)
This might be of interest to some on this list (even though this is a few days old already):
https://www.snailload.com/
Probing queuing delay to identify which (of a small set of) youtube videos the victim was watching...
The set-up is not straight forward and a bit contrived, but still interessing what can be learned just from the temporal buffer filling patterns...
P.S.: Resent due to picking the wrong e-mail address the first time around, sorry
reply other threads:[~2024-06-26 9:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ED1986B6-B9E6-4569-8C9A-6E91F9308CDD@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox