On Thu, Dec 5, 2013 at 10:38 AM, Tyler Hicks <tyhicks@xxxxxxxxxxxxx> wrote: > On 2013-12-05 19:32:11, Catalin Ionita wrote: >> Hi, > > Hello! > >> >> I've been working for some time on a solution to integrate ecryptfs >> in Android. Due to some Android specifics and license problems I had >> to rewrite the userspace tools. > > I really wish these problems would have been brought up on this list. > Fragmentation of the utilities is a bad thing. There's already enough of > it in ecryptfs-utils (mount.ecryptfs vs mount.ecryptfs_private) but now > there's an entirely new package, too. > >> Also, for a nice finish touch, I have >> implemented Android user data encryption from top (including a minimal >> GUI) to bottom on a Nexus 4 running latest AOSP kitkat. > > Very cool. Looking forward to checking it out. > >> >> I'm looking for volunteers to test, review or contribute to Android >> userspace tools that I've built. The project is stored at >> https://github.com/catalinionita/Ecryptfs-Tools-for-Android > > First, I'd like to explore merging the two code bases. Can you lay out > the reasons for writing from scratch? If he is looking to upstream it, Google prefers things under Apache 2.0. However, this doesn't mean that other licenses are instantly a no either. For example, checkpolicy. On the code side, are their dependencies to other libraries that the userspace tools require that perhaps Android does not have or has incompatible versions? Another reason would perhaps be size, lets see what the author says. Also, I could swear I remember reading something about him asking about Android ecryptfs before. > > As the kernel maintainer, I don't expect to have the bandwidth to update > and test both utils packages when kernel changes occur. It would be > great if ecryptfs-utils and efs-tools lived in the same tree (and shared > the majority of their code). > > Tyler -- Respectfully, William C Roberts -- To unsubscribe from this list: send the line "unsubscribe ecryptfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
