From: Ronald G Minnich <rminnich@lanl.gov>
To: "King, Steven R" <steven.r.king@intel.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [BUNDLE] Testing a simpler inter-domain transport
Date: Sun, 12 Feb 2006 16:59:07 -0700 [thread overview]
Message-ID: <43EFCBCB.3010309@lanl.gov> (raw)
In-Reply-To: <44BDAFB888F59F408FAE3CC35AB4704102FCD61D@orsmsx409>
King, Steven R wrote:
> Shared page LAN is much less secure than a real LAN. Any domain
> attached to the shared page, i.e. in the LAN, can modify any frame "in
> flight" on the page. Recipients have no confidence that the received
> frame is actually what the sender sent.
yes, this discussion came up some time ago (I noticed it when i was
doing the Plan 9 port) and I think the conclusion was "yep, it's an
issue". I am not sure where it all went -- I have not yet started the
xen 3.0 port for plan 9.
ron
next prev parent reply other threads:[~2006-02-12 23:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 23:39 [BUNDLE] Testing a simpler inter-domain transport King, Steven R
2006-02-12 23:59 ` Ronald G Minnich [this message]
2006-02-13 2:32 ` Rusty Russell
2006-02-13 9:38 ` Daniel Veillard
-- strict thread matches above, loose matches on Subject: below --
2006-02-13 3:24 King, Steven R
2006-02-13 3:47 ` Rusty Russell
2006-02-10 17:54 Magenheimer, Dan (HP Labs Fort Collins)
2006-02-08 1:31 Magenheimer, Dan (HP Labs Fort Collins)
2006-02-08 2:55 ` Hollis Blanchard
2006-02-10 3:15 ` Rusty Russell
2006-02-06 21:38 Magenheimer, Dan (HP Labs Fort Collins)
2006-02-06 20:48 Yang, Fred
2006-02-06 20:01 Magenheimer, Dan (HP Labs Fort Collins)
2006-02-07 0:10 ` Rusty Russell
2006-02-05 3:38 Rusty Russell
2006-02-05 10:26 ` NAHieu
2006-02-05 11:13 ` Rusty Russell
2006-02-05 16:56 ` Anthony Liguori
2006-02-06 4:40 ` Rusty Russell
2006-02-08 10:12 ` Daniel Veillard
2006-02-08 10:23 ` Rusty Russell
2006-02-08 10:34 ` Muli Ben-Yehuda
2006-02-08 10:46 ` Daniel Veillard
2006-02-08 10:54 ` Muli Ben-Yehuda
2006-02-08 17:49 ` Matt Mackall
2006-02-08 11:04 ` Rusty Russell
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=43EFCBCB.3010309@lanl.gov \
--to=rminnich@lanl.gov \
--cc=rusty@rustcorp.com.au \
--cc=steven.r.king@intel.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.