2014-02-2017:10, SandeepKsinha : > > > > On Thu, Feb 20, 2014 at 2:27 PM, freeman <[email protected] > <mailto:[email protected]>> 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
_______________________________________________ Kernelnewbies mailing list [email protected] http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
