[guardian-dev] Fwd: [tor-dev] Size issues with Orbot statically linking OpenSSL
Nathan of Guardian
nathan at guardianproject.info
Sun Jan 15 09:51:07 EST 2012
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.
tor-dev mailing list
tor-dev at lists.torproject.org
More information about the Guardian-dev