From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] remark about http://www.freeoszoo.org
Date: Mon, 4 Oct 2004 12:43:42 +0100 [thread overview]
Message-ID: <200410041243.42601.paul@codesourcery.com> (raw)
In-Reply-To: <20041004112907.GB18436@xi.wantstofly.org>
On Monday 04 October 2004 12:29, Lennert Buytenhek wrote:
> On Mon, Oct 04, 2004 at 02:50:31AM -0400, Karl Magdsick wrote:
> > Free OS Zoo suggests using dd with the seek= option in the _specific_
> > case of Linux, which appears to be safe. My comment was explicitly a
> > note of caution in the _general_ case.
>
> Yep. As well as:
>
> "[...] the image will likely contain parts of deleted files from
> the host OS."
>
> Just curious, do you have an example of any such system where this
> would be the case? I don't know of any system that doesn't support
> sparse files and doesn't pad out the file with zeroes if you
> truncate(2) it to be bigger.
I'm fairly sure any half-sane OS will zero the "sparse" bits of a file on
allocation. IIRC even Windows NT does zero the sparse bits of a file.
Failure to do so would be a rather large security hole, effectively allowing
unprivileged users to read privileged data.
IMHO the original post is unjustified paranoia, rather than reasonable
caution.
Paul
next prev parent reply other threads:[~2004-10-04 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-02 13:16 [Qemu-devel] remark about http://www.freeoszoo.org albi
2004-10-03 17:47 ` Karl Magdsick
2004-10-03 19:21 ` Lennert Buytenhek
2004-10-04 6:50 ` Karl Magdsick
2004-10-04 11:29 ` Lennert Buytenhek
2004-10-04 11:43 ` Paul Brook [this message]
2004-10-04 4:09 ` Brad Campbell
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=200410041243.42601.paul@codesourcery.com \
--to=paul@codesourcery.com \
--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.