From: linux-os <linux-os@analogic.com>
To: Vineet Joglekar <vintya@excite.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
linux-c-programming@vger.kernel.org
Subject: Re: when and where shall I encrypt dentry?
Date: Wed, 2 Feb 2005 09:14:53 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.61.0502020905330.16140@chaos.analogic.com> (raw)
In-Reply-To: <20050202134901.9926C3E12@xprdmailfe6.nwk.excite.com>
The correct place to encrypt or decrypt ANYTHING is
just before access to the "outside" world, i.e., in the
case of a file-system, the reads and writes to the
storage device (disk drive). You are in a world of
hurt if you intend to encrypt 'data' and directories
separately.
If you need to use an existing file-system and then
encrypt it, you use the same technique but your
"storage device" is a "container file" that you mount
using the loop device. This allows you to have an
encrypted file-system below some mount-point and
a normal file-system above.
FYI, there are existing tools/code that allow one to
mount an encrypted file-system. Perhaps your masters
project just got easier?
On Wed, 2 Feb 2005, Vineet Joglekar wrote:
>
> Hi all,
>
> I am trying to add some cryptographic functionality to ext2 file system for my masters project. I am working with kernel 2.4.21
>
> Along with regular files, I intend to encrypt directory contents too. For reading I guess the function ext2_get_page in fs/ext2/dir.c is used. Hence I can put my decryption routine in that function. Is that correct?
>
> I was trying to look for the routine which writes the dentry on disk, but was unable to find it. I found out that the function d_instantiate is used to fill in inode information for a dentry, but unable to see when it is written on disk. I suppose that I have to encrypt the dentry just before writing on to the disk, as if i encrypt it before, other functions using it wont be able to access until they decrypt. So please help me with this, that when and where shall I encrypt the directory contents.
>
> Thanks and regards,
>
> Vineet
>
> _______________________________________________
> Join Excite! - http://www.excite.com
> The most personalized portal on the Web!
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Cheers,
Dick Johnson
Penguin : Linux version 2.6.10 on an i686 machine (5537.79 BogoMips).
Notice : All mail here is now cached for review by Dictator Bush.
98.36% of all statistics are fiction.
prev parent reply other threads:[~2005-02-02 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 13:49 when and where shall I encrypt dentry? Vineet Joglekar
2005-02-02 14:14 ` linux-os [this message]
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=Pine.LNX.4.61.0502020905330.16140@chaos.analogic.com \
--to=linux-os@analogic.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vintya@excite.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).