[tor-bugs] #10281 [Applications/Tor Browser]: Investigate usage of alternate memory allocators and memory hardening options
Tor Bug Tracker & Wiki
blackhole at torproject.org
Fri Dec 9 01:16:15 UTC 2016
#10281: Investigate usage of alternate memory allocators and memory hardening
options
-------------------------------------------------+-------------------------
Reporter: mikeperry | Owner:
| arthuredelstein
Type: enhancement | Status:
| needs_information
Priority: Very High | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: tbb-security, tbb-hardened, | Actual Points:
TorBrowserTeam201612R |
Parent ID: | Points:
Reviewer: | Sponsor:
| SponsorU
-------------------------------------------------+-------------------------
Comment (by arthuredelstein):
Replying to [comment:38 gk]:
> Two other things I am wondering: should we have this on the hardened
series first, only? (sounds like a good idea to me)
That's OK with me! I'm not sure how it will interact with ASan, though.
> Are we okay with the jemalloc4 ESR45 ships or do we think we should need
to backport the patches already landed on m-c (or are about to land)?
There was work done in comment:29 for that already and I am wondering
about the severity of all the bugfixes that landed in jemalloc4
meanwhile...
Unfortunately, when I include just the 4 patches from comment:29 and use
`MOZ_JEMALLOC4=1`, I get build errors. I think jemalloc didn't actually
build in comment:29, because the patches that implemented --enable-
jemalloc=4 weren't included. I'm working on backporting more patches to
try to get the latest jemalloc to build. It's a bit complex.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10281#comment:40>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list