| To: | Nathan Scott <nathans@xxxxxxx> |
|---|---|
| Subject: | Re: XFS information leak during crash |
| From: | Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> |
| Date: | Thu, 03 Nov 2005 12:45:49 +0000 |
| Cc: | Jan Kasprzak <kas@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20051103111115.C6081538@xxxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <20051102212722.GC6759@xxxxxxxxxx> <20051103101107.O6239737@xxxxxxxxxxxxxxxxxxxxxxxx> <20051102233629.GD6759@xxxxxxxxxx> <20051103104956.B6081538@xxxxxxxxxxxxxxxxxxxxxxxx> <20051103000317.GE6759@xxxxxxxxxx> <20051103111115.C6081538@xxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS information leak during crash, Glen Overby |
|---|---|
| Next by Date: | Re: XFS corruption on 2.4.28, Eric Sandeen |
| Previous by Thread: | Re: XFS information leak during crash, Nathan Scott |
| Next by Thread: | Re: XFS information leak during crash, Theodore Ts'o |
| Indexes: | [Date] [Thread] [Top] [All Lists] |