From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: [Battlemesh] Cross-Router Covert Channels
Date: Thu, 22 Aug 2019 17:47:33 -0700 [thread overview]
Message-ID: <CAA93jw7N9=WpD0J63ttFVZtAyP+ZoM-WNnW1c-B06f-U709caw@mail.gmail.com> (raw)
In-Reply-To: <f72d51d1-7a8b-c37a-7e81-f9d9540e3dfb@tnode.com>
We need to go back to passenger pigeons.
---------- Forwarded message ---------
From: Mitar <mitar@tnode.com>
Date: Thu, Aug 22, 2019 at 5:34 PM
Subject: [Battlemesh] Cross-Router Covert Channels
To: Battlemesh <battlemesh@ml.ninux.org>
Hi!
Leaking data between guest and private network on the same router, even
if they are otherwise separated:
https://www.usenix.org/system/files/woot19-paper_ovadia.pdf
Mitar
--
http://mitar.tnode.com/
https://twitter.com/mitar_m
_______________________________________________
Battlemesh mailing list
Battlemesh@ml.ninux.org
https://ml.ninux.org/mailman/listinfo/battlemesh
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
parent reply other threads:[~2019-08-23 0:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <f72d51d1-7a8b-c37a-7e81-f9d9540e3dfb@tnode.com>]
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7N9=WpD0J63ttFVZtAyP+ZoM-WNnW1c-B06f-U709caw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@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