xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Elena <elena.junk@gmail.com>
To: xen-devel@lists.xensource.com
Subject: intercept interrupts from guest domains and find rootkits
Date: Tue, 9 Feb 2010 20:59:22 +0100	[thread overview]
Message-ID: <984b7bd91002091159g7843147aye00aa16a21f90fa0@mail.gmail.com> (raw)

Hello!!

I'd like to refer to this post: "RE: [Xen-devel] Re: How to intercept
interrupts from guest domains"
made by "Mads Bergdal" on 21 Sep 2006 in this list.

Mads try to intercept hypercalls made by a guest domain, from hypervisor.
I made this, modifying xen source (entry.S) and print on dmesg the
number of hypercall.

My question is: if in a guest domain an intruder install a rootkit
(for example an IDT hooking), my hypercall interception on Dom0 can
estabilished that there was a violation to that guest?? Is any rootkit
installed on guest detectable by my hypercall interception (for
example an rootkit that make a specific sequence of hypercalls)?

I hope that it isn't so complicated and I thanks you in advance for
comprehension.

Regards,
Elena

                 reply	other threads:[~2010-02-09 19:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=984b7bd91002091159g7843147aye00aa16a21f90fa0@mail.gmail.com \
    --to=elena.junk@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).