Hi there,<br><br>First of all thanks for helping me last time with my mipsel build of Tor with statically linked OpenSSL.<br>It&#39;s running fine and we&#39;re waiting for the last review of the bandwith-checking scripts before they go live.<br>
<br>The second cluster we prepare will consist of low-powered PowerPC devices 250MHz/256MB Ram/8MB Flash.<br>This time Tor will dynamically link to OpenSSL (libcrypto.so.1.0.0 and libssl.so.1.0.0) because there are also other programs depending on it.<br>
Because the devices have very limited flash-space the binaries and libraries have to be as small as possible.<br>Tor 0.2.3.19-rc is only 550KB with only libevent staticly linked in (stripped and bz2 compressed).<br>When run, it will be extracted to /tmp, executed and then deleted (since /tmp runs in RAM).<br>
<br>It runs very well so far :)<br><br>However the OpenSSL libraries are quite large for this system and they don&#39;t fit in at the moment.<br>libcrypto.so.1.0.0 is 1.9MB and libssl.so.1.0.0 is 375KB (stripped).<br><br>
Our goal is to run Tor both as client and router and therefor I&#39;d like to know the absolute minimum required ciphers for doing so.<br>We&#39;ve currently compiled OpenSSL 1.0.1 with:<br><br>NM=powerpc-gnu-nm CC=powerpc-linux-gnu-gcc RANLIB=powerpc-linux-gnu-ranlib AR=powerpc-linux-gnu-ar \<br>
./Configure --prefix=/home/mastag/root --openssldir=/home/mastag/root/lib/ssl \<br>shared threads zlib enable-tlsext no-ssl2 no-dso no-idea no-mdc2 no-rc5 \<br>no-engines no-hw linux-ppc \<br><br>From the OpenSSL documentation it seems that no-hw and no-engines leaves out support for hardware crypto engines so those are safe to set (our devices don&#39;t have them).<br>
<br>Could anybody provide us with more &quot;no-&quot; options for ciphers we can skip?<br>Thanks alot!<br><br>