From: James Muir <muir.james.a@gmail.com>
To: ecryptfs@vger.kernel.org
Subject: porting to android
Date: Sun, 15 Sep 2013 00:05:20 -0400 [thread overview]
Message-ID: <52353200.9040101@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hello list,
I'm interested in porting some of the ecryptfs userland tools to android
- -- specifically, I want to get the mount and umount utilities working.
I've hacked around a bit and see that there is a dependency with Mozilla
NSS (e.g. in the functions ecryptfs_wrap_passphrase and
ecryptfs_unwrap_passphrase). Apparently, NSS can be built for Android,
but before I go further down the hole, I wondered if someone more
familiar with the user tools might have some perspective to share. My
impression is that getting the tools working on Android shouldn't
be too difficult, but I wonder if I am being too optimistic... if I
sort out NSS, will it be smooth sailing?
Note the ./configure script suggests that it is possible to build
against gcrypt rather than NSS ("--disable-nss Build against
gcrypt rather than NSS"), but I suspect that configuration hasn't
actually been implemented yet. Has anyone built the user tools using
gcrypt?
More generally, has anyone worked on porting these utilities
previously? I've googled and found mention that ecryptfs is used on
the Droid X but the source code was not published:
http://android.stackexchange.com/questions/20105/motorola-droidx-ecryptfs-related-sources
Also, the following blueprint suggests that an android port has been on
the Linaro backlog for some time:
https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-integrate-ecryptfs
thanks for your help,
- -James
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlI1MgAACgkQ4Arkm0Hw/FLFYgCbBoS8p2yHQjpx0b/zW9xzPxRs
d98AoIGvDYK3EK35zISXxc9I3tXQnWAb
=8Nr5
-----END PGP SIGNATURE-----
next reply other threads:[~2013-09-15 4:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-15 4:05 James Muir [this message]
[not found] ` <CAFftDdq-DQSzGDqKSDGCpvenGp_KtCgR0hzfX1uqSGnfmKAiqg@mail.gmail.com>
2013-09-16 18:24 ` porting to android James Muir
[not found] ` <CAFftDdrmF6gvk_Vh8AReUrXVRLCs25SdFBZyqUhHv-tid5KDSg@mail.gmail.com>
2013-09-18 21:36 ` James Muir
2013-09-20 17:43 ` James Muir
2013-10-03 15:44 ` Dustin Kirkland
2013-10-08 15:12 ` James Muir
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=52353200.9040101@gmail.com \
--to=muir.james.a@gmail.com \
--cc=ecryptfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.