All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hopwood <david.nospam.hopwood@blueyonder.co.uk>
To: xen-devel@lists.sourceforge.net
Subject: Re: Fw: Xen on /. again
Date: Fri, 21 Jan 2005 00:48:58 +0000	[thread overview]
Message-ID: <41F0517A.5080503@blueyonder.co.uk> (raw)
In-Reply-To: <200501202241.06631.maw48@cl.cam.ac.uk>

Mark Williamson wrote:
>>Also, I suppose you will wish to prevent covert channels between
>>domains, e.g. domains communicating using various timing attacks (I move
>>the disk head to the other end of the disk if I wish to tell you
>>something), or by allocating/freeing certains parts of memory.
>>
>>How much will you need to dumb down the VMs view of what is going on in
>>the machine to achieve this (not expose real time information, not
>>expose real page tables), and how much of a VMM will there be left when
>>you are done?
> 
> Well domains are not aware of each other's memory usage, so I wouldn't have 
> thought that allocation / exposing real page tables would matter.  (Except 
> dom0 can of course see everything if it wants).

Information about other domains' memory usage is leaked via the
hardware->physical mapping.

> Timing related attacks are somewhat trickier to eliminate covert channels in, 
> although some randomisation can limit the bandwidth.

Eliminating covert channels is completely infeasible. I don't see any
value in aiming for this. It's not a useful security property in most
circumstances.

-- 
David Hopwood <david.nospam.hopwood@blueyonder.co.uk>



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

  parent reply	other threads:[~2005-01-21  0:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19 19:57 Fw: Xen on /. again Trent Jaeger
2005-01-20 22:11 ` Jacob Gorm Hansen
2005-01-20 22:41   ` Mark Williamson
2005-01-20 23:30     ` Jacob Gorm Hansen
2005-01-21  0:14       ` Mark Williamson
2005-01-21  0:48     ` David Hopwood [this message]
2005-01-21  0:55       ` Mark Williamson
2005-01-21  1:32         ` David Hopwood
2005-01-21  1:38           ` Mark Williamson
2005-01-21  1:09       ` Reiner Sailer
2005-01-21  7:53       ` Steven Hand
2005-01-21  8:08         ` Steven Hand
2005-01-21  2:35     ` Jody Belka
2005-01-21 11:06       ` Mark A. Williamson
2005-01-21 11:22       ` Mark A. Williamson
2005-01-21 23:37         ` Jody Belka
2005-01-22 17:20           ` Mark Williamson
2005-01-22 18:16             ` Jody Belka
2005-01-23 17:52               ` Multiple netif device channels (was Fw: Xen on /. again) Mark Williamson
2005-01-25  0:32                 ` Jody Belka
2005-01-25 13:52                   ` Mark Williamson
2005-01-25 23:06                 ` Multiple netif device channels Jody Belka
2005-01-26 20:36                   ` Mark Williamson
2005-01-27  0:51                     ` Jody Belka
2005-01-27 14:00                       ` Jody Belka
2005-01-21  0:19   ` Fw: Xen on /. again Trent Jaeger
  -- strict thread matches above, loose matches on Subject: below --
2005-01-21  1:25 Ian Pratt

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=41F0517A.5080503@blueyonder.co.uk \
    --to=david.nospam.hopwood@blueyonder.co.uk \
    --cc=xen-devel@lists.sourceforge.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 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.