From: Jan Kasprzak <kas@fi.muni.cz>
To: Nathan Scott <nathans@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: XFS information leak during crash
Date: Thu, 3 Nov 2005 01:03:17 +0100 [thread overview]
Message-ID: <20051103000317.GE6759@fi.muni.cz> (raw)
In-Reply-To: <20051103104956.B6081538@wobbly.melbourne.sgi.com>
Nathan Scott wrote:
: XFS behaves as most filesystems do and
: will write over the top of existing data.
OK, thanks for the clarification.
: XFS also rewrites files in-place. You will never get someone else's
: current data (that would be metadata corruption...),
Of course.
: it would only
: ever be uninitialised, previously-free space.
Yes, but an old data from previously deleted files
(sendmail's temporary files, vim save files, etc) may contain
a sensitive information.
-Y.
--
| Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> |
| GPG: ID 1024/D3498839 Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
| http://www.fi.muni.cz/~kas/ Journal: http://www.fi.muni.cz/~kas/blog/ |
> Specs are a basis for _talking_about_ things. But they are _not_ a basis <
> for implementing software. --Linus Torvalds <
next prev parent reply other threads:[~2005-11-03 0:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 21:27 Jan Kasprzak
2005-11-02 23:11 ` Nathan Scott
2005-11-02 23:36 ` Jan Kasprzak
2005-11-02 23:49 ` Nathan Scott
2005-11-03 0:03 ` Jan Kasprzak [this message]
2005-11-03 0:11 ` Nathan Scott
2005-11-03 12:45 ` Alan Cox
2005-11-03 17:05 ` Theodore Ts'o
2005-11-09 16:55 ` Jan Kasprzak
2005-11-03 0:19 ` Mikulas Patocka
2005-11-03 0:38 ` Nathan Scott
2005-11-03 0:41 ` Glen Overby
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=20051103000317.GE6759@fi.muni.cz \
--to=kas@fi.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=nathans@sgi.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
all inboxes | Powered by JetHome®