Re: [tor-dev] Putting onion services behind a third-party TCP proxy

2019-08-19 Thread teor
> On 20 Aug 2019, at 13:31, Pop Chunhapanya wrote: > > Hi Tim, > >> >> TCPProxy protocol host:port >> >> Tor will use the given protocol to make all its OR (SSL) connections through >> a TCP proxy on host:port, rather than connecting directly to servers. You >> may want to set FascistFirewa

Re: [tor-dev] Putting onion services behind a third-party TCP proxy

2019-08-19 Thread Pop Chunhapanya
Hi Tim, > TCPProxy protocol host:port > > > Tor will use the given protocol to make all its OR (SSL) connections > through a TCP proxy on host:port, rather than connecting directly to > servers. You may want to set FascistFirewall to restrict the set of ports > you might try to connect to, if you

Re: [tor-dev] TBB Memory Allocator choice fingerprint implications

2019-08-19 Thread Shawn Webb
Hey Tom, Thank you for your response. You've made some great points. My response is inline. On Mon, Aug 19, 2019 at 04:09:36PM +, Tom Ritter wrote: > Okay I'm going to try and clear up a lot of misconceptions and stuff > here. I don't own Firefox's memory allocator but I have worked in it, >

Re: [tor-dev] TBB Memory Allocator choice fingerprint implications

2019-08-19 Thread Patrick Schleizer
Btw Hardened Malloc does not require recompilation of TBB. Compilation of Hardened Malloc is easy. https://github.com/GrapheneOS/hardened_malloc It then can be used with TBB or any application using LD_PRELOAD environment variable. LD_PRELOAD='/path/to/libhardened_malloc.so' /path/to/program J

Re: [tor-dev] TBB Memory Allocator choice fingerprint implications

2019-08-19 Thread Tom Ritter
Okay I'm going to try and clear up a lot of misconceptions and stuff here. I don't own Firefox's memory allocator but I have worked in it, recently, and am one of the people who are working on hardening it. Firefox's memory allocator is not jemalloc. It's probably better referred to as mozjemallo