|
osdir.com mailing list archive |
|
Subject: Re: Data Shredding on a Journal Filesystem - msg#00200List: file-systems.reiserfs.general> > of course, putting sensitive files on a loopback encrypted fs is better. > > then you don't have to worry about plaintext laying around, and you don't > > need shred or wipe. > > You also need to be careful so that this sensitive data won't get into swap. also, .bash_history can reviel filenames. -- Tom Vier <tmv@xxxxxxxxxxx> DSA Key ID 0xE6CB97DA Thread at a glance:
Previous Message by Date: click to view message previewRe: Data Shredding on a Journal FilesystemHello! On Thu, Sep 26, 2002 at 02:13:32AM -0400, Tom Vier wrote: > of course, putting sensitive files on a loopback encrypted fs is better. > then you don't have to worry about plaintext laying around, and you don't > need shred or wipe. You also need to be careful so that this sensitive data won't get into swap. Bye, Oleg Next Message by Date: click to view message previewRe: Reserved BlocksHi, Oleg Drokin: > That's right. But the program that writes into that file is setuid program. > And blocks are allocated by that setuid program. Blocks (possibly more than one) may also be allocated by opening the file, especially if it happens to have a long name. If you want limits, use quotas. They may not be perfect, but at least they work. ;-) -- Matthias Urlichs | noris network AG | http://smurf.noris.de/ Previous Message by Thread: click to view message previewRe: Data Shredding on a Journal FilesystemHello! On Thu, Sep 26, 2002 at 02:13:32AM -0400, Tom Vier wrote: > of course, putting sensitive files on a loopback encrypted fs is better. > then you don't have to worry about plaintext laying around, and you don't > need shred or wipe. You also need to be careful so that this sensitive data won't get into swap. Bye, Oleg Next Message by Thread: click to view message previewRE: Data Shredding on a Journal FilesystemHi Oleg. I'm using the standard journaling from 2.4.19 - metadata for recovery from power failures. We are also using tails at this time. I have been investigating the use of -o notails as a performance improvement; however, I need to weigh that against disk space usage as well. -----Original Message----- From: Oleg Drokin [mailto:green@xxxxxxxxxxx] Sent: Wednesday, September 25, 2002 3:30 AM To: berthiaume_wayne@xxxxxxx Cc: reiserfs-list@xxxxxxxxxxx Subject: Re: [reiserfs-list] Data Shredding on a Journal Filesystem Hello! On Tue, Sep 24, 2002 at 05:12:03PM -0400, berthiaume_wayne@xxxxxxx wrote: > Hello fellow ReiserFS fans. I'm in search of a data shredder for use > on reiserfs and am wondering if anyone knows of one. It would need to > effectively remove any trace both in the journal and on the disk itself any > and all data pertaining to a file. I'm not sure, but I thought at one time > Hans was talking about something this himself. I have looked at shred() but > it does not work with journalling filesystems. shred should work just fine with reiserfs in case you did not enable data journaling mode and you have tails disabled. The only thing that may be left on disk is filename and blocks in which file itself was stored. Bye, Oleg Loading Comments...
|
|
