From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Amos Kong <akong@redhat.com>,
autotest@test.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM-test: Add a new test: privacy test
Date: Tue, 15 Mar 2011 01:29:43 -0300 [thread overview]
Message-ID: <1300163383.2705.27.camel@freedom> (raw)
In-Reply-To: <20110228113228.GG28006@redhat.com>
On Mon, 2011-02-28 at 13:32 +0200, Michael S. Tsirkin wrote:
> On Mon, Feb 28, 2011 at 07:20:38PM +0800, Amos Kong wrote:
> > Communicate between two vms, and try to capture packages from another vm in
> > the same lan.
> > This test used tcpdump, so we need limit it with Linux guests.
> >
> > Signed-off-by: Amos Kong <akong@redhat.com>
>
> I don't think there's any such privacy guarantee for a plain
> bridged setup: the bridge might flood packets to
> all endpoints sometimes, and rx mac address filters
> even if present are guest controllable so they represent
> a performance optimization, not a privacy guarantee.
>
> This is analogous to a physical shared lan: any box can
> enable promisc mode and snoop on packets.
>
> You need vlans, or netfilter, or some other filtering
> if you want to enforce privacy.
Amos, per Michael's comments, perhaps we should put vm1 and vm2 on a
vlan and vm3 on a different vlan to have a more valid packet privacy
testing? I'll refrain from adding this test to the upstream tree until
we have a more satisfactory test/solution.
prev parent reply other threads:[~2011-03-15 4:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 11:20 [PATCH] KVM-test: Add a new test: privacy test Amos Kong
2011-02-28 11:32 ` Michael S. Tsirkin
2011-03-15 4:29 ` Lucas Meneghel Rodrigues [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1300163383.2705.27.camel@freedom \
--to=lmr@redhat.com \
--cc=akong@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
/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