[guardian-dev] Fwd: [tor-dev] Size issues with Orbot statically linking OpenSSL

Stephen Lombardo sjlombardo at zetetic.net
Mon Jan 16 10:00:39 EST 2012

Hi Nathan,

You might be able to cut down the size of the openssl libraries by trimming
out some features that would go unused by the application, i.e. via
the configure systems options like no-asm, no-krb5, no-<cipher> etc.
Alternately, if you have a custom build setup, you may be able to do the
same via defines like NO_IDEA. Also, 8 MB sounds a bit large. If memory
serves, the last time I looked at a single architecture openssl build for
armv6, the resulting archives were just north 3 MB combined. Is openssl a
debug build, or does LibEvent account for a large portion of that 8MB?


On Sun, Jan 15, 2012 at 9:51 AM, Nathan of Guardian <
nathan at guardianproject.info> wrote:

> Any thoughts on the issue below would be much appreciated. If we turn on
> installLocation="auto" we can allow for external storage, but then we
> have to limit our low end device support to Android 2.2/platform-8.
> -------- Original Message --------
> Subject: [tor-dev] Size issues with Orbot statically linking OpenSSL
> Date: Sun, 15 Jan 2012 09:50:06 -0500
> From: Nathan Freitas <nathan at freitas.net>
> Reply-To: tor-dev at lists.torproject.org
> To: tor-dev at lists.torproject.org
> With the recent problems related to SSLv3 with versions of OpenSSL less
> than 1.0.0f, we have been investigating how to deal with this on Android
> for Orbot. Historically, we have used the version of OpenSSL provided by
> the Android device itself, which has ranged from 0.9.8 to 1.0.0e (the
> latest on ICS 4.0).
> We have now produced a build of OpenSSL 1.0.0f with the necessary
> Android patches, and statically linked this into the Tor binary we ship
> inside of Orbot. (We already do this for LibEvent, since that is not
> included in Android itself). With both OpenSSL and LibEvent linked, the
> Tor binary increases from 3MB to about 8MB.
> 8MB is not terrible, but once you include the Orbot app, Privoxy and
> other files, we are getting into the 10MB+ range.
> I think this is all fine, and we can enable users to run the app from a
> secured partition on their external storage, but I did just want to run
> this by all of you to see if there are any options for limiting the size
> of libssl.a and libcrypto.a, and the resulting Tor binary.
> Thx!
> +n8fr8
> _______________________________________________
> tor-dev mailing list
> tor-dev at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
> _______________________________________________
> Guardian-dev mailing list
> Post: Guardian-dev at lists.mayfirst.org
> List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev
> To Unsubscribe
>        Send email to:  Guardian-dev-unsubscribe at lists.mayfirst.org
>        Or visit:
> https://lists.mayfirst.org/mailman/options/guardian-dev/sjlombardo%40zetetic.net
> You are subscribed as: sjlombardo at zetetic.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mayfirst.org/pipermail/guardian-dev/attachments/20120116/a2ce1730/attachment.htm>

More information about the Guardian-dev mailing list