public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Matthew J. Fanto" <mattf@mattjf.com>
To: Lars Marowsky-Bree <lmb@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: The Ext3sj Filesystem
Date: Wed, 30 Oct 2002 16:20:18 -0500	[thread overview]
Message-ID: <200210301620.18326.mattf@mattjf.com> (raw)
In-Reply-To: <20021030205652.GC22178@marowsky-bree.de>

On Wednesday 30 October 2002 03:56 pm, Lars Marowsky-Bree wrote:

> Do you encrypt before the data has hit the data journal or after? Does that
> work for mmap etc?

I have not finished journaling support yet, but it will encrypt before it hits 
the journal. Yes, there should be no problem with mmap.

>
> This sounds like something you might want to abstract into a generic
> architecture to be shared with the loop device code, or anything which
> might need encryption in the kernel. Otherwise it is a PITA to maintain.

I will be going over the cryptoAPI code tonight and seeing if I can change the 
crypto routines to use the cryptoAPI, as it would be much easier to maintain. 

> And I thought some of those algorithms were strictly signature / hash
> algorithms, but you never stop learning ;-)

The SHA algorithms, as well as MD5 are used for message digests (hashing). 
This is used to transform the key prior to passing the key off to the 
specific algorithms key setup functions. I have also thought about, albeit 
not too much, about using message digests/signatures as a file integreity 
mechanism. 

I should also mention that deletion of files on ext3sj will use DoD standards 
for secure file deletion by overwriting the data with all 0's, all 1's, and 
then random data. So, before you delete a file, make sure you really want to 
delete it, because there won't be a way to recover it. 

-Matthew J. Fanto

  reply	other threads:[~2002-10-30 21:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30 19:34 The Ext3sj Filesystem Matthew J. Fanto
2002-10-30 20:00 ` Andreas Dilger
2002-10-30 21:33   ` Matthew J. Fanto
2002-10-31 16:21     ` Henning P. Schmiedehausen
2002-11-01  1:32   ` Bill Davidsen
2002-10-30 20:28 ` Rik van Riel
2002-10-31 16:36   ` Nicholas Wourms
2002-10-30 20:56 ` Lars Marowsky-Bree
2002-10-30 21:20   ` Matthew J. Fanto [this message]
2002-10-30 21:34 ` Bill Davidsen
2002-10-30 21:40   ` Matthew J. Fanto
2002-11-01  4:41 ` Theodore Ts'o
2002-11-01  5:14   ` Matthew J. Fanto

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=200210301620.18326.mattf@mattjf.com \
    --to=mattf@mattjf.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lmb@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox