From: freeman.zhang1992@gmail.com (freeman)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [Help] How to Replace File Operations in File System?
Date: Mon, 17 Feb 2014 08:59:15 +0800 [thread overview]
Message-ID: <53015EE3.1080101@gmail.com> (raw)
In-Reply-To: <99785.1392418190@turing-police.cc.vt.edu>
On 15 Feb 2014, Valdis.Kletnieks at vt.edu said:
> On Thu, 13 Feb 2014 21:26:43 +0800, freeman said:
>
>> eCryptfs, I have this idea to design a simplified module(not
>> another filesystem) to do transparent en/decrypting, by
> Doing it transparently is harder than it looks. Key management is a bitch.
>
> (Hint - there's a reason why ecryptfs does it the way it does, rather than
> the simpler way you're attempting to do it...)
Hi Valdis,
Thanks for your hint! There is no wonder that I got stuck when studying
key management of eCryptfs.I think I should pay much more attention
to it.
Any idea of how to deal with key management? openPGP file format,
multitudinous authentication in eCryptfs really make me give up!
Regards
Freeman
next prev parent reply other threads:[~2014-02-17 0:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 2:10 [Help] How to Replace File Operations in File System? freeman
2014-02-13 6:44 ` Abhijit Chandrakant Pawar
2014-02-13 6:59 ` Saket Sinha
2014-02-13 11:47 ` Rishi Agrawal
2014-02-13 13:28 ` freeman
2014-02-17 8:06 ` Rishi Agrawal
2014-02-18 4:34 ` freeman
[not found] ` <CADDndfPhe=iHKtB0_eTYpoAAUJDTkOchUakbOyKveVdkAOLrMQ@mail.gmail.com>
2014-02-20 1:32 ` freeman
2014-02-20 7:31 ` Rishi Agrawal
2014-02-20 8:57 ` freeman
2014-02-20 9:10 ` SandeepKsinha
2014-02-20 9:48 ` freeman
2014-02-20 9:51 ` SandeepKsinha
2014-02-20 15:32 ` Valdis.Kletnieks at vt.edu
2014-02-24 1:52 ` Freeman Zhang
2014-02-13 13:26 ` freeman
2014-02-14 22:49 ` Valdis.Kletnieks at vt.edu
2014-02-17 0:59 ` freeman [this message]
2014-02-17 2:50 ` Saket Sinha
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=53015EE3.1080101@gmail.com \
--to=freeman.zhang1992@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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).