All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Have any ideas about how to detect whether a program is running inside QEMU?
Date: Thu, 6 Jul 2006 11:56:00 +0100	[thread overview]
Message-ID: <20060706105600.GA17018@mail.shareable.org> (raw)
In-Reply-To: <c13b6c000607060018y10cf5c8fwdce320e34fb0f333@mail.gmail.com>

James Lau wrote:
>    My  program  is  a utility for internet payment. It takes an important
>    role  in  the  payment  process  to  ensure  security.  One of the key
>    functions  is  that the program should detect which machine is paying.
>    So  while  virtual  machine  (like  QEMU) is present, it can cheat the
>    program.
> 
>    Checking   the   hard   disk  model,  cpu  type,  and  other  hardward
>    informations makes little sense.  Because the users or the hackers can
>    easily  modify  these informations. So I need a QEMU internal checking
>    method that hackers can't easily bypass.

But hackers can easily modify QEMU source.  So how can you depend on
any feature of QEMU for your security checks?

-- Jamie

  parent reply	other threads:[~2006-07-06 10:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06  5:04 [Qemu-devel] Have any ideas about how to detect whether a program is running inside QEMU? James Lau
2006-07-06  6:48 ` Natalia Portillo
2006-07-06  6:55 ` John R. Hogerhuis
2006-07-06  7:18   ` James Lau
2006-07-06  8:20     ` Kevin F. Quinn
2006-07-06 10:33     ` Jan Marten Simons
2006-07-07  2:12       ` James Lau
2006-07-06 10:56     ` Jamie Lokier [this message]
2006-07-06 20:46     ` Daniel Serpell
2006-07-06 23:21       ` Kevin F. Quinn
2006-07-07  8:07         ` G Portokalidis
2006-07-07 20:36           ` [Qemu-devel] " Anthony Liguori
2006-07-07  0:06       ` Anthony Liguori

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=20060706105600.GA17018@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=qemu-devel@nongnu.org \
    /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.