From: Tyler Hicks <tyhicks@canonical.com>
To: Catalin Ionita <io.catalin@gmail.com>
Cc: ecryptfs@vger.kernel.org
Subject: Re: Looking for volunteers to test and review ecryptfs integration with Android
Date: Thu, 5 Dec 2013 10:38:07 -0800 [thread overview]
Message-ID: <20131205183806.GC16300@boyd> (raw)
In-Reply-To: <CAGE04zTe4VP_hDju9E9m8ONbTPZyv_pZ=9CPkd5Ke8aOK9Ddyg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
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?
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
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-05 18:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 17:32 Looking for volunteers to test and review ecryptfs integration with Android Catalin Ionita
2013-12-05 17:40 ` William Roberts
2013-12-05 18:38 ` Tyler Hicks [this message]
2013-12-05 18:57 ` William Roberts
2013-12-05 19:11 ` Tyler Hicks
2013-12-06 8:02 ` Catalin Ionita
2013-12-06 8:20 ` Catalin Ionita
[not found] ` <CAFftDdraQs9AUVfOVjGLNx2V4X4P+w3upDNPSm_p=T5Jjhd2jA@mail.gmail.com>
2013-12-06 15:15 ` Catalin Ionita
2013-12-06 15:17 ` Catalin Ionita
2013-12-06 16:22 ` William Roberts
2013-12-06 22:26 ` Catalin Ionita
2013-12-06 22:38 ` William Roberts
2013-12-09 9:53 ` Catalin Ionita
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=20131205183806.GC16300@boyd \
--to=tyhicks@canonical.com \
--cc=ecryptfs@vger.kernel.org \
--cc=io.catalin@gmail.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