All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Day <ncmike@us.ibm.com>
To: Reiner Sailer <sailer@us.ibm.com>
Cc: xen-devel@lists.xensource.com, xense-devel@lists.xensource.com,
	Bryan D Payne <bdpayne@us.ibm.com>
Subject: Re: RFC: virtual network access control
Date: Fri, 28 Jul 2006 19:43:20 -0400	[thread overview]
Message-ID: <20060728234320.GC6701@localhost.localdomain> (raw)
In-Reply-To: <OF4F1B646F.86700717-ON852571B9.005A7C7A-852571B9.005AB707@us.ibm.com>

On 28/07/06 12:30 -0400, Reiner Sailer wrote:

>   > In terms of cost, an extra hypercall per packet will have measurable
>   > cost, at least in CPU usage, for high-bandwidth network transfers.
>   >
>   >   -- Keir
>   >
>   You only make the decision once for the first packet exchanged between
>   two interfaces. Afterwards you reuse this decision for this interface
>   pair (local cache). You basically have the cost of looking up a
>   decision locally.

This is a key principle of "shype" - that they hypervisor authorizes
the channel when it to be set up. As long as the channel persists
unchaged (no additional parties, not policy modifications) there is no
need to perform further authorization. It performs a different level
of authorization than packet filtering does, and it is another layer
of depth in a multi-layer defense.

Mike

  reply	other threads:[~2006-07-28 23:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 20:51 RFC: virtual network access control Reiner Sailer
2006-07-27 20:57 ` Caitlin Bestler
2006-07-28  9:18 ` Keir Fraser
2006-07-28 14:17   ` Reiner Sailer
2006-07-28 14:31     ` Keir Fraser
2006-07-28 14:56       ` Reiner Sailer
2006-07-28 15:06         ` Keir Fraser
2006-07-28 16:30           ` Reiner Sailer
2006-07-28 23:43             ` Mike Day [this message]
2006-07-28 14:47     ` Harry Butterworth
2006-07-28 15:13     ` Gerd Hoffmann
2006-07-28 19:49       ` [Xense-devel] " Reiner Sailer

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=20060728234320.GC6701@localhost.localdomain \
    --to=ncmike@us.ibm.com \
    --cc=bdpayne@us.ibm.com \
    --cc=sailer@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xense-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.