kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: freeman.zhang1992@gmail.com (freeman)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [Help] How to Replace File Operations in File System?
Date: Thu, 20 Feb 2014 17:48:07 +0800	[thread overview]
Message-ID: <5305CF57.7090905@gmail.com> (raw)
In-Reply-To: <CAMeSd+FD8okRbtyLadLZjDpMQ0_eZ=z2kVmNZiZszF6nAbCN6Q@mail.gmail.com>


2014-02-2017:10, SandeepKsinha :
>
>
>
> On Thu, Feb 20, 2014 at 2:27 PM, freeman <freeman.zhang1992@gmail.com
> <mailto:freeman.zhang1992@gmail.com>> wrote:
>
>
>     2014-02-20 15:31, Rishi Agrawal :
>>     Hi,
>>
>>     I went through your readme. Some questions.
>>
>>     1. How are you encrypting the files? Is it done by the encryptfs
>>     or you are doing it in your module.
>>
>>     2. How can the user selectively encrypt the files in the system.
>>
>>
>>     -- 
>>     Regards,
>>     Rishi Agrawal
>     Hi Rishi,
>
>     Sorry about the fuzziness.
>
>     #1 I plan to do the encryption in my module, but encrypting
>     functions aren't added to it yet. As I mentioned in readme,
>     module now just simply pass-through operations to the original
>     file system.
>
>     #2 It seems that the user cannot select specific file to encrypt
>     inside one directory :-( . However he may specify a directory
>     then we can encrypt all the file inside it. Namely, the granularity
>     is directory, not file. Besides, subdirectory is not supported at
>     present.
>
>
> Why does it even matter - inode vs directory? Is it because you store
> the encryption metadata in the dirent and not the inode?
>  
>
>
>     Regards
>     Freeman
>
>
>
> -- 
> Regards,
> Sandeep.
>
> "To learn is to change. Education is a process that changes the learner."
Hi Sandeep,

Actually I haven't got that far...
However as I planed it, I don't want involve the user too much-
just to keep simple. I plan to build a safe box, and people throw
personal things into it. That's all.
I want to use it with Android devices. Will complex implementation
build barrier for ebedded system?
Any suggestions?

Regards
Freeman Zhang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140220/988b0ea9/attachment.html 

  reply	other threads:[~2014-02-20  9:48 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 [this message]
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
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=5305CF57.7090905@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).