[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-dev] TBB Memory Allocator choice fingerprint implications
On Sat, 17 Aug 2019 at 15:06, procmem@xxxxxxxxxx <procmem@xxxxxxxxxx> wrote:
> Question for the Tor Browser experts. Do you know if it is possible to
> remotely fingerprint the browser based on the memory allocator it is
> using? (via JS or content rendering)
Fingerprint what aspect of the browser/machine?
> We are thinking of switching Tor Browser to use the minimalist and
> security oriented hardened_malloc written by Daniel Micay. Thanks.
I wouldn't advise giving up partitioning for.... what exactly? What
features does this allocator have that 68's jemalloc doesn't?
-tom
_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev