From: "Theodore Ts'o" <tytso@mit.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Nathan Scott <nathans@sgi.com>, Jan Kasprzak <kas@fi.muni.cz>,
linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: XFS information leak during crash
Date: Thu, 3 Nov 2005 12:05:27 -0500 [thread overview]
Message-ID: <20051103170527.GA7113@thunk.org> (raw)
In-Reply-To: <1131021949.18848.21.camel@localhost.localdomain>
On Thu, Nov 03, 2005 at 12:45:49PM +0000, Alan Cox wrote:
> On Iau, 2005-11-03 at 11:11 +1100, Nathan Scott wrote:
> > On Thu, Nov 03, 2005 at 01:03:17AM +0100, Jan Kasprzak wrote:
> > > : 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.
> >
> > Indeed. But this is a generic issue affecting most filesystems;
> > its not specific to XFS as your original mail claimed.
>
> Very true. You can use ext3 in data journalling mode if this is a
> concern but that guarantee has a performance cost
The default ordered journalling mode solves this problem at a much
lower cost.
- Ted
next prev parent reply other threads:[~2005-11-03 17:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 21:27 XFS information leak during crash 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
2005-11-03 0:11 ` Nathan Scott
2005-11-03 12:45 ` Alan Cox
2005-11-03 17:05 ` Theodore Ts'o [this message]
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=20051103170527.GA7113@thunk.org \
--to=tytso@mit.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=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 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.