From: Gaurav Maheshbhai Patel <gmpatel@learn.senecac.on.ca>
To: xen-devel@lists.xensource.com
Subject: Re: Instant Xen guest (guest-magic tool)
Date: Sun, 15 Apr 2007 05:59:47 -0500 [thread overview]
Message-ID: <f5eef7976285.4621bf53@learn.senecac.on.ca> (raw)
In-Reply-To: <20070415001906.GA6757@steve.org.uk>
Thankyou very much steve,
Its very helpful.
Gaurav
----- Original Message -----
From: Steve Kemp <steve@steve.org.uk>
Date: Saturday, April 14, 2007 7:19 pm
Subject: Re: [Xen-devel] Instant Xen guest (guest-magic tool)
To: Gaurav Maheshbhai Patel <gmpatel@learn.senecac.on.ca>
Cc: xen-devel@lists.xensource.com
> On Sat, Apr 14, 2007 at 09:51:42AM -0500, Gaurav Maheshbhai Patel
> wrote:
> > The comment on /tmp/guestmagic was really good.
> > I was wondering what if we use /tmp/$$
> >
> > > commands.getoutput('xm list > /tmp/$$')
> >
> > Is it create the same problem as /tmp/guestmagic?
>
> Pretty much. Process IDs are still *predictable* since they
> tend to be sequential under most systems.
>
> Still this is better than a static name. You should really
> use a pipe. If you can't then use a secure filename which
> can't be guessed by a local user.
>
> This is pretty off-topic for the xen list though, so I'll
> just suggest you look at the Secure Programming Howto:
>
> http://www.dwheeler.com/secure-programs/Secure-Programs-
> HOWTO/index.html
> Specifically the section on temporary files being used in
> races.
>
> Steve
> --
>
next prev parent reply other threads:[~2007-04-15 10:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 2:51 Instant Xen guest (guest-magic tool) Gaurav Maheshbhai Patel
2007-04-11 9:06 ` Steve Kemp
2007-04-11 18:54 ` Gaurav Maheshbhai Patel
2007-04-11 22:42 ` Steve Kemp
2007-04-12 16:17 ` Gaurav Maheshbhai Patel
2007-04-12 18:52 ` Steve Kemp
2007-04-14 14:51 ` Gaurav Maheshbhai Patel
2007-04-15 0:19 ` Steve Kemp
2007-04-15 10:59 ` Gaurav Maheshbhai Patel [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-17 22:51 Tom Wisniewski
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=f5eef7976285.4621bf53@learn.senecac.on.ca \
--to=gmpatel@learn.senecac.on.ca \
--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.