Specifying tor's libevent and openssl directories adds RPATH to resulting binary
The configure script to Tor has arguments that allow the specification of a non-standard libevent and openssl (--with-libevent-dir=PATH and --with-openssl-dir=PATH). Unfortunately, these arguments also add -rpath to the linking step for these directories, which creates an RPATH entry in the resulting tor binary such that these directories become part of the library search path. For TBB, this results in creating the ability for code injection via creation of .so files in /home/ubuntu/install/, as reported by this troll
I suppose we can set LIBRARY_PATH and C_INCLUDE_PATH prior to configure/make instead, which I think will just cause gcc to search these directories during build without emitting an RPATH for them.