From: James Muir <muir.james.a@gmail.com>
To: William Roberts <bill.c.roberts@gmail.com>
Cc: ecryptfs@vger.kernel.org
Subject: Re: porting to android
Date: Wed, 18 Sep 2013 17:36:03 -0400 [thread overview]
Message-ID: <523A1CC3.3090607@gmail.com> (raw)
In-Reply-To: <CAFftDdrmF6gvk_Vh8AReUrXVRLCs25SdFBZyqUhHv-tid5KDSg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/16/2013 02:34 PM, William Roberts wrote:
> my tools were generic... I did it over a year ago. I am having a
> hard time remembering what, or how I did it.
>
That's too bad. I could use some help :-)
I've had limited success so far. I've if-def'd out the Mozilla NSS
stuff and am just concentrating on getting mount.ecryptfs working when
options are passed directly to it:
mount.ecryptfs lower upper \
-o ecryptfs_cipher=aes,ecryptfs_key_bytes=16,...
There are three libraries that mount.ecryptfs needs: libkeyutils,
libecryptfs, and libecryptfs_key_mod_passphrase. I've managed to
build each of those after some minor changes (for android-arm). With
those libraries available, I can then build the mount utility.
However, when I try the above command on my device I get an error from
the function ecryptfs_eval_decision_graph() :-(
Here is a more general question for the list: is this forum more for
the ecryptfs kernel mod devs? or do the ecryptfs user-tool devs hang
out here, too?
- -James M
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlI6HLsACgkQ4Arkm0Hw/FIg+QCghuQJadNtJm5rRL9QID7ugJwf
P4sAnjbNzYw52jhPMdtkFZgPBBRiCasz
=NVGB
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-09-18 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-15 4:05 porting to android James Muir
[not found] ` <CAFftDdq-DQSzGDqKSDGCpvenGp_KtCgR0hzfX1uqSGnfmKAiqg@mail.gmail.com>
2013-09-16 18:24 ` James Muir
[not found] ` <CAFftDdrmF6gvk_Vh8AReUrXVRLCs25SdFBZyqUhHv-tid5KDSg@mail.gmail.com>
2013-09-18 21:36 ` James Muir [this message]
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=523A1CC3.3090607@gmail.com \
--to=muir.james.a@gmail.com \
--cc=bill.c.roberts@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.