All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Oleg Drokin <green@namesys.com>
Cc: Jason Holt <jason@lunkwill.org>, reiserfs-list@namesys.com
Subject: Re: securely deleting files
Date: Mon, 12 May 2003 14:39:51 +0400	[thread overview]
Message-ID: <3EBF79F7.8090501@namesys.com> (raw)
In-Reply-To: <20030512075022.GC21604@namesys.com>

Oleg Drokin wrote:

>Hello!
>
>On Tue, May 06, 2003 at 05:37:13AM +0000, Jason Holt wrote:
>
>  
>
>>Now, a good friend of mine pointed out that part of the space on a filesystem
>>is kept aside just for root, so you may want to fill the disk up as root.  
>>(Is this actually a concern?  Can blocks which used to hold user data end up
>>being reserved?)  
>>    
>>
>
>Yes they can.
>No, we don't have such (supported) feature in reiserfsv3 yet.
>
You meant the reserved space for root?

>Also if the file was deleted, but something still have open filehandle to it (or hardlink),
>its blocks are not freed at rm time and therefore filling all the free space won't help.
>There are other caveats.
>
>  
>
>>Also, if your sensitive file was in memory recently it might have been swapped
>>out, in which case it may still be in the swap partition.  I have a program
>>which fills up all available *memory* as well, and I could post the source
>>here if everyone's interested.
>>    
>>
>
>If the program that used the file and still have the copy of it is still running,
>no matter how much you eat all the ram, the file still can end up in swap.
>
>The program that fills up all available memory is called "tail". Just run
>"tail /dev/zero" and enjoy ;) (this does not work on FreeBSD, though).
>
>Bye,
>    Oleg
>
>
>  
>


-- 
Hans



  reply	other threads:[~2003-05-12 10:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06  5:37 securely deleting files Jason Holt
2003-05-06 10:37 ` Hans Reiser
2003-05-12  7:50 ` Oleg Drokin
2003-05-12 10:39   ` Hans Reiser [this message]
2003-05-12 10:44     ` Oleg Drokin

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=3EBF79F7.8090501@namesys.com \
    --to=reiser@namesys.com \
    --cc=green@namesys.com \
    --cc=jason@lunkwill.org \
    --cc=reiserfs-list@namesys.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.