From: Rupesh Thakare <rupesh@clusterfs.com>
To: "Wolber, Richard C" <richard.c.wolber@boeing.com>
Cc: Andreas Dilger <adilger@clusterfs.com>,
Nikolai Joukov <kolya@cs.sunysb.edu>,
Erik Mouw <erik@harddisk-recovery.com>,
Samuel Tardieu <sam@rfc1149.net>,
linux-ext4@vger.kernel.org
Subject: Re: Shred mount option for ext4?
Date: Mon, 20 Nov 2006 16:22:12 +0530 [thread overview]
Message-ID: <456188DC.5030107@clusterfs.com> (raw)
In-Reply-To: <8C7C41A176AC0B468BEFB2EFD9BDAB9902426639@XCH-NW-5V2.nw.nos.boeing.com>
Wolber, Richard C wrote:
>> On Wednesday, November 01, 2006 8:17 AM Andreas Dilger Wrote:
>>
>> Did anyone discuss doing this with crypto instead of actually
>> overwriting the whole file? It would be pretty easy to store
>> a per-file crypto key in each inode as an EA, then to
>> "delete" the file all that would be needed would be to erase
>> the key in a secure matter (which is a great deal easier
>> because inodes don't move around on disk).
>>
>
> If it's cheap to delete the keys, it's also cheap to harvest
> the keys. A per file crypto-key lowers the barrier to entry.
>
That's true. But can't we combine the advantages of single-secure-key
and per-file krypto key ?
Can't we have a half single-secure-key combined with half
per-file-krypto ? Key management overhead is not
worse than that for single-secure-key. This gives offers same security
with ease for shredding.
Cheers,
Rupesh
> This is Schneier 101.
>
>
> ..Chuck..
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2006-11-20 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 20:14 Shred mount option for ext4? Nikolai Joukov
2006-11-01 16:17 ` Andreas Dilger
2006-11-01 16:38 ` Ric Wheeler
2006-11-01 16:52 ` Nikolai Joukov
2006-11-01 17:20 ` Erez Zadok
2006-11-01 16:57 ` Wolber, Richard C
2006-11-20 10:52 ` Rupesh Thakare [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-31 10:36 Samuel Tardieu
2006-10-31 12:32 ` Erik Mouw
2006-10-31 13:02 ` Samuel Tardieu
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=456188DC.5030107@clusterfs.com \
--to=rupesh@clusterfs.com \
--cc=adilger@clusterfs.com \
--cc=erik@harddisk-recovery.com \
--cc=kolya@cs.sunysb.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=richard.c.wolber@boeing.com \
--cc=sam@rfc1149.net \
/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.