[tor-dev] TBB Memory Allocator choice fingerprint implications
tom at ritter.vg
Sat Aug 17 21:17:40 UTC 2019
On Sat, 17 Aug 2019 at 15:06, procmem at riseup.net <procmem at riseup.net> 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?
More information about the tor-dev