Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T14:06:08Zhttps://gitlab.torproject.org/legacy/trac/-/issues/1880Enhanced Security Suggestion2020-06-13T14:06:08ZTracEnhanced Security SuggestionCould a random traffic delay be incorporated into the routing algorithm, in order to thwart traffic timing on the nodes. Random packing of data might also be necessary to avoid the detection of packet sizes through the nodes?
**Trac**:...Could a random traffic delay be incorporated into the routing algorithm, in order to thwart traffic timing on the nodes. Random packing of data might also be necessary to avoid the detection of packet sizes through the nodes?
**Trac**:
**Username**: foreverTor: very long termhttps://gitlab.torproject.org/legacy/trac/-/issues/2878Don't bootstrap from an old consensus if we're about to replace it2020-06-13T15:19:11ZSebastian HahnDon't bootstrap from an old consensus if we're about to replace itStarting up maint-0.2.2 with an old data dir, I got this:
```
[notice] We now have enough directory information to build circuits.
[notice] Bootstrapped 80%: Connecting to the Tor network.
[notice] Bootstrapped 85%: Finishing handshake ...Starting up maint-0.2.2 with an old data dir, I got this:
```
[notice] We now have enough directory information to build circuits.
[notice] Bootstrapped 80%: Connecting to the Tor network.
[notice] Bootstrapped 85%: Finishing handshake with first hop.
[notice] Bootstrapped 90%: Establishing a Tor circuit.
[notice] Tor has successfully opened a circuit. Looks like client functionality is working.
[notice] Bootstrapped 100%: Done.
[warn] Please upgrade! This version of Tor (0.2.2.19-alpha) is not recommended, according to the directory authorities. Recommended versions are: 0.2.1.29,0.2.1.30,0.2.2.21-alpha,0.2.2.22-alpha,0.2.2.23-alpha
[notice] Our directory information is no longer up-to-date enough to build circuits: We have only 0/2268 usable descriptors.
[notice] I learned some more directory information, but not enough to build a circuit: We have only 0/2268 usable descriptors.
[notice] Tor has successfully opened a circuit. Looks like client functionality is working.
[notice] I learned some more directory information, but not enough to build a circuit: We have only 96/2268 usable descriptors.
[notice] I learned some more directory information, but not enough to build a circuit: We have only 192/2268 usable descriptors.
[notice] I learned some more directory information, but not enough to build a circuit: We have only 288/2268 usable descriptors.
[notice] I learned some more directory information, but not enough to build a circuit: We have only 384/2268 usable descriptors.
[notice] I learned some more directory information, but not enough to build a circuit: We have only 480/2268 usable descriptors.
[notice] We now have enough directory information to build circuits.
```
First we make a circuit, then immediately we are say we don't have enough data to make a circuit and get a little spammy about that, too. Maybe there's an easy fix, if not we should postpone this for 0.2.3.xTor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/3600Prevent redirects from transmitting+storing cookies+identifiers2020-06-16T01:27:32ZMike PerryPrevent redirects from transmitting+storing cookies+identifiersI've been using RequestPolicy for so long I'd not realized that redirects have been getting more and more transparent. In Firefox 4/5, the loading indications are impossible to differentiate between redirects and 3rd party loads.
There ...I've been using RequestPolicy for so long I'd not realized that redirects have been getting more and more transparent. In Firefox 4/5, the loading indications are impossible to differentiate between redirects and 3rd party loads.
There does not appear to be any obvious about:config options to enable more prompting either. We may have to dig into the RequestPolicy source to see how they do this.
Redirect notification is important if we're going to try to keep 3rd party cookies disabled (or dual-keyed). If redirects are 100% transparent, there's little point in disabling 3rd party cookies.
NoScript has some options for notifying in the case of JS redirects. We'll probably want to enable those options in TBB, too.https://gitlab.torproject.org/legacy/trac/-/issues/4580Some Tor clients go nuts requesting the consensus if there is no recent enoug...2020-06-13T15:11:29ZRoger DingledineSome Tor clients go nuts requesting the consensus if there is no recent enough consensusYesterday we failed to make a consensus for whatever reason.
Soon after, we (the directory authorities) started getting bombed by begindir requests. I'm not sure what they were requesting, but early analysis shows they were requesting a...Yesterday we failed to make a consensus for whatever reason.
Soon after, we (the directory authorities) started getting bombed by begindir requests. I'm not sure what they were requesting, but early analysis shows they were requesting a consensus. Most of the requests sent their begindir cell but never got their actual HTTP request through.
When I noticed, moria1 was at 2+ gigs of ram. I did a kill -USR1 and it spent an hour dumping 195000 conns, and I killed it at that point. No idea how many conns it had total. They were almost all linked conns, e.g.:
```
Nov 25 02:34:45.000 [info] Conn 195295 (socket -1) type 5 (Exit), state 3 (open), created 145 secs ago
Nov 25 02:34:45.000 [info] Conn 195295 is to [x]:1.
Nov 25 02:34:45.000 [info] Conn 195295: 0 bytes waiting on inbuf (len 0, last read 145 secs ago)
Nov 25 02:34:45.000 [info] Conn 195295: 0 bytes waiting on outbuf (len 0, last written 145 secs ago)
Nov 25 02:34:45.000 [info] Conn 195295 has Exit-ward circuit: circID 0 (other side 46154), state 3 (open), born 1322201975:
Nov 25 02:34:45.000 [info] Conn 195296 (socket -1) type 9 (Directory), state 5 (waiting for command), created 145 secs ago
Nov 25 02:34:45.000 [info] Conn 195296 is to [x]:0.
Nov 25 02:34:45.000 [info] Conn 195296: 0 bytes waiting on inbuf (len 0, last read 145 secs ago)
Nov 25 02:34:45.000 [info] Conn 195296: 0 bytes waiting on outbuf (len 0, last written 145 secs ago)
```
For this particular [x], there were 16665 conns open because of it.
But only 27 of them were OR conns, e.g.:
```
Nov 25 01:26:05.000 [info] Conn 121 (socket 371) type 4 (OR), state 8 (open), created 704 secs ago
Nov 25 01:26:05.000 [info] Conn 121 is to [x]:62067.
Nov 25 01:26:05.000 [info] Conn 121: 496 bytes waiting on inbuf (len 32736, last read 10 secs ago)
Nov 25 01:26:05.000 [info] Conn 121: 0 bytes waiting on outbuf (len 0, last written 10 secs ago)
Nov 25 01:26:05.000 [info] Conn 121: 0/18437 bytes used on OpenSSL read buffer; 0/18698 bytes used on write buffer.
Nov 25 01:26:05.000 [info] Conn 121 has App-ward circuit: circID 36152 (other side 0), state 3 (open), born 1322201666:
```
```
Nov 25 01:26:35.000 [info] Conn 1530 (socket 163) type 4 (OR), state 8 (open), created 208 secs ago
Nov 25 01:26:35.000 [info] Conn 1530 is to [x]:62767.
Nov 25 01:26:35.000 [info] Conn 1530: 0 bytes waiting on inbuf (len 0, last read 10 secs ago)
Nov 25 01:26:35.000 [info] Conn 1530: 0 bytes waiting on outbuf (len 0, last written 95 secs ago)
Nov 25 01:26:35.000 [info] Conn 1530: 0/18437 bytes used on OpenSSL read buffer; 0/18698 bytes used on write buffer.
Nov 25 01:26:35.000 [info] Conn 1530 has App-ward circuit: circID 53174 (other side 0), state 3 (open), born 1322202160:
```
```
Nov 25 01:27:25.000 [info] Conn 3762 (socket 480) type 4 (OR), state 8 (open), created 408 secs ago
Nov 25 01:27:25.000 [info] Conn 3762 is to [x]:62152.
Nov 25 01:27:25.000 [info] Conn 3762: 432 bytes waiting on inbuf (len 32736, last read 10 secs ago)
Nov 25 01:27:25.000 [info] Conn 3762: 32768 bytes waiting on outbuf (len 36576, last written 10 secs ago)
Nov 25 01:27:25.000 [info] Conn 3762: 0/18437 bytes used on OpenSSL read buffer; 0/18698 bytes used on write buffer.
Nov 25 01:27:25.000 [info] Conn 3762 has App-ward circuit: circID 57857 (other side 0), state 3 (open), born 1322201977:
```
```
Nov 25 01:28:39.000 [info] Conn 7024 (socket 192) type 4 (OR), state 8 (open), created 107 secs ago
Nov 25 01:28:39.000 [info] Conn 7024 is to [x]:62866.
Nov 25 01:28:39.000 [info] Conn 7024: 0 bytes waiting on inbuf (len 0, last read 98 secs ago)
Nov 25 01:28:39.000 [info] Conn 7024: 0 bytes waiting on outbuf (len 0, last written 99 secs ago)
Nov 25 01:28:39.000 [info] Conn 7024: 0/18437 bytes used on OpenSSL read buffer; 0/18698 bytes used on write buffer.
```
```
Nov 25 01:32:14.000 [info] Conn 17016 (socket 417) type 4 (OR), state 8 (open), created 202 secs ago
Nov 25 01:32:14.000 [info] Conn 17016 is to [x]:62772.
Nov 25 01:32:14.000 [info] Conn 17016: 480 bytes waiting on inbuf (len 32736, last read 10 secs ago)
Nov 25 01:32:14.000 [info] Conn 17016: 32768 bytes waiting on outbuf (len 36576, last written 10 secs ago)
Nov 25 01:32:14.000 [info] Conn 17016: 0/18437 bytes used on OpenSSL read buffer; 0/18698 bytes used on write buffer.
Nov 25 01:32:14.000 [info] Conn 17016 has App-ward circuit: circID 40388 (other side 0), state 3 (open), born 1322202167:
```
So my first thought is that moria1 just can't keep up with hearing all these new requests, and also pumping bytes out to the requestor, and things just queue up, which uses ram, which makes seeks slower, lather rinse repeat.
Is there a Tor client version out there that asks for a consensus without checking if it has already asked for a consensus?Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/6217Mozilla updates queries happen at regular intervals2020-06-15T23:14:30ZcypherpunksMozilla updates queries happen at regular intervalsThis was reported to Mozilla but I thought it would probably not get considered properly unless reported here:
https://bugzilla.mozilla.org/show_bug.cgi?id=755284
>Fingerprintable information in update behavior
>If update checks are e...This was reported to Mozilla but I thought it would probably not get considered properly unless reported here:
https://bugzilla.mozilla.org/show_bug.cgi?id=755284
>Fingerprintable information in update behavior
>If update checks are enabled, Firefox seems to perform them at exactly the interval specified in the app.update.interval preference. (Tested with a 120-second interval and leaving the browser running.) This leads to a minor potential way of fingerprinting users on anonymizing networks like Tor because output relays can observe an update check occurring at a precise second corresponding to a particular user.
>I realize this is a minor issue and difficult to exploit, but the solution is also appropriately minor. I assume it will be enough to simply randomize the scheduled time of next update (or the time stored in the lastUpdateTime settings, whichever) by up to 5% of the update interval. This fix will still preserve the user-set meaning of the app.update.interval setting, on average.https://gitlab.torproject.org/legacy/trac/-/issues/6767tor crashes with Assertion smartlist_get(rl->old_routers, idx) == sd failed2020-06-13T14:28:12ZLeonid Evdokimovtor crashes with Assertion smartlist_get(rl->old_routers, idx) == sd failedI started my gateway with stderr redirected to syslog and got following crash:
```
Sep 2 12:30:07 OpenWrt cron.info crond[708]: crond: USER root pid 1794 cmd /root/tor-watchdog.sh
Sep 2 12:43:19 OpenWrt daemon.err Tor[1280]: routerlist...I started my gateway with stderr redirected to syslog and got following crash:
```
Sep 2 12:30:07 OpenWrt cron.info crond[708]: crond: USER root pid 1794 cmd /root/tor-watchdog.sh
Sep 2 12:43:19 OpenWrt daemon.err Tor[1280]: routerlist_remove_old(): Bug: routerlist.c:3004: routerlist_remove_old: Assertion idx == sd->routerlist_index failed; aborting.
Sep 2 12:43:21 OpenWrt user.notice tor.stdout: routerlist.c:3004 routerlist_remove_old: Assertion idx == sd->routerlist_index failed; aborting.
Sep 2 12:45:01 OpenWrt cron.info crond[708]: crond: USER root pid 1797 cmd /root/tor-watchdog.sh
Sep 2 12:45:01 OpenWrt user.notice Tor.watchdog: pidfile exists and process is missing - start
Sep 2 12:45:02 OpenWrt user.notice Tor.init: Sep 02 12:45:02.684 [notice] Tor v0.2.2.37 (git-fce6eb1c44e87bc2). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux mips)
```
OpenWrt package versions: libopenssl - 1.0.1c-1, tor - 0.2.2.37-1
openssl build information:
```
root@OpenWrt:~# strings /usr/lib/libcrypto.so.1.0.0 | grep gcc
libgcc_s.so.1
mipsel-openwrt-linux-uclibc-gcc -fPIC -DOPENSSL_PIC -DZLIB_SHARED -DZLIB -DDSO_DLFCN -DHAVE_DLFCN_H -I/home/fnord/slave/brcm47xx/build/staging_dir/target-mipsel_uClibc-0.9.33.2/usr/include -I/home/fnord/slave/brcm47xx/build/staging_dir/target-mipsel_uClibc-0.9.33.2/include -I/home/fnord/slave/brcm47xx/build/staging_dir/toolchain-mipsel_gcc-4.6-linaro_uClibc-0.9.33.2/usr/include -I/home/fnord/slave/brcm47xx/build/staging_dir/toolchain-mipsel_gcc-4.6-linaro_uClibc-0.9.33.2/include -DOPENSSL_SMALL_FOOTPRINT -DHAVE_CRYPTODEV -DOPENSSL_NO_ERR -DTERMIO -Os -pipe -mips32 -mtune=mips32 -fno-caller-saves -fhonour-copts -Wno-error=unused-but-set-variable -msoft-float -fpic -DOPENSSL_THREADS -pthread -D_REENTRANT -D_THREAD_SAFE -D_THREADSAFE -fomit-frame-pointer -Wall
```Tor: 0.3.3.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/8185circuit_package_relay_cell(): Bug: outgoing relay cell has n_chan==NULL. Drop...2020-06-13T15:16:59ZTraccircuit_package_relay_cell(): Bug: outgoing relay cell has n_chan==NULL. Dropping.Don't know whether the above message is related to bugs #8093 or #6252 (if so, apologies!), but decided to report this anyway. The full message is:
[warn] {BUG} circuit_package_relay_cell(): Bug: outgoing relay cell has n_chan==NULL. Dr...Don't know whether the above message is related to bugs #8093 or #6252 (if so, apologies!), but decided to report this anyway. The full message is:
[warn] {BUG} circuit_package_relay_cell(): Bug: outgoing relay cell has n_chan==NULL. Dropping.
There are no particular circumstances which I've noticed this message to appear (in fact, I've noticed it only when checking the tor logs a couple of hours later) - tor has been running more than a day at that point.
**Trac**:
**Username**: mr-4Tor: 0.2.9.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/8725resource:// URIs leak information2020-06-16T00:46:26ZTracresource:// URIs leak informationHere's a bug in Firefox that may be able to identify users of Tor Browser Bundle:
!https://bugzilla.mozilla.org/show_bug.cgi?id=863246
**Trac**:
**Username**: holizzHere's a bug in Firefox that may be able to identify users of Tor Browser Bundle:
!https://bugzilla.mozilla.org/show_bug.cgi?id=863246
**Trac**:
**Username**: holizzhttps://gitlab.torproject.org/legacy/trac/-/issues/9521"new identity" leaks memory in eventSuppressor.suppressEventHandling()2020-06-16T01:27:35ZRoger Dingledine"new identity" leaks memory in eventSuppressor.suppressEventHandling()According to skruffy, each tab that's open when you click 'new identity' contributes to more lost memory.
For normal tabs, when you close them, eventually the memory from them garbage collects or otherwise returns to the system. For tab...According to skruffy, each tab that's open when you click 'new identity' contributes to more lost memory.
For normal tabs, when you close them, eventually the memory from them garbage collects or otherwise returns to the system. For tabs closed by new identity, it remains lost.https://gitlab.torproject.org/legacy/trac/-/issues/10416Tor won't start on Windows when path contains non-ascii characters2022-03-16T20:55:25ZTracTor won't start on Windows when path contains non-ascii charactersWhen trying to start the TBB from the following path:
C:\Users\kuncaŭščyna\Downloads\Tor Browser\
got the following error:
Vidalia detected that the Tor software exited unexpectedly.
Please check the message log for recent warning or ...When trying to start the TBB from the following path:
C:\Users\kuncaŭščyna\Downloads\Tor Browser\
got the following error:
Vidalia detected that the Tor software exited unexpectedly.
Please check the message log for recent warning or error messages.
Here's the log:
Dez 16 18:27:21.431 [Hinweis] Tor v0.2.3.25 (git-17c24b3118224d65) running on Windows 7.
Dez 16 18:27:21.431 [Hinweis] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Dez 16 18:27:21.431 [Warnung] Unable to open configuration file "C:\Users\kuncauscyna\Downloads\Tor Browser\Data\Tor\torrc".
Dez 16 18:27:21.431 [Fehler] Reading config failed--see warnings above.
Diacritics were obviously "simplified" which created inexisting path.
I know Windows is not recommened for anonymity. But some people use TBB on Win only for censorship circumvention. The easiest solution is simply to add a message to log like:
Unable to open configuration file "C:\Users\kuncauscyna\Downloads\Tor Browser\Data\Tor\torrc". Please check that the path contains only ascii symbols.
But much better would be to fix it to process correctly path in unicode.
**Trac**:
**Username**: iktsuarpokTor: unspecifiedAlexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/legacy/trac/-/issues/10467URLs are leaked to third party if they contain typos2020-06-15T23:17:34ZTracURLs are leaked to third party if they contain typosOpen a new tab in the Tor Browser and type "https;//www.wikipedia.org" into the URL field (note the typo - a semicolon instead of a colon)
The Tor Browser jumps to startpage.com and searches it for "https;//www.wikipedia.org"
Users may...Open a new tab in the Tor Browser and type "https;//www.wikipedia.org" into the URL field (note the typo - a semicolon instead of a colon)
The Tor Browser jumps to startpage.com and searches it for "https;//www.wikipedia.org"
Users may make typos - and I think there is no need to leak URLs with typos to a third party (startpage). You should patch Firefox so that anything typed into the URL field is never sent to a third party.
There is already a special field for startpage search in the navigation toolbar - so there is no need to use the URL field for searches.
**Trac**:
**Username**: torarhttps://gitlab.torproject.org/legacy/trac/-/issues/10498Get only the NoScript we want to our users2020-06-15T23:17:38ZcypherpunksGet only the NoScript we want to our usersNoscript is Firefox extension, known for years security tool and simplest way to stop stuff. Author of Noscript never used [public repository](http://forums.informaction.com/viewtopic.php?p=10981#p10981) for demonstrating development pro...Noscript is Firefox extension, known for years security tool and simplest way to stop stuff. Author of Noscript never used [public repository](http://forums.informaction.com/viewtopic.php?p=10981#p10981) for demonstrating development progress, all known code was available as standalone archive or file from [AMO](https://addons.mozilla.org/). However, author used to sign components of archive [before 2.6.6.9 version](http://hackademix.net/2013/07/20/noscript-and-flashgot-unsigned/). All we have now to try guess files wasn't modified on a way, and still chance to recreate history of development by hands or by 3rd party [repository for versions difference](https://github.com/avian2/noscript)
TBB takes Noscript from servers of AMO during building and run-time addon updates. Do we trust them so much?https://gitlab.torproject.org/legacy/trac/-/issues/11254Tor Browser bundle v3.5 fails to clean up cancelled downloads in Temp folder2020-06-16T00:45:29ZTracTor Browser bundle v3.5 fails to clean up cancelled downloads in Temp folder1. Run TBB v3.5.3
2. Click on a link to download an archive or any file type not natively handled by the browser
3. Wait for the download to complete
4. Observe that <random>.ext.part file is created containing entire file contents in th...1. Run TBB v3.5.3
2. Click on a link to download an archive or any file type not natively handled by the browser
3. Wait for the download to complete
4. Observe that <random>.ext.part file is created containing entire file contents in the system's %temp% folder.
4. In the Open/Save dialog box click Cancel.
5. Observe that the temp-created file is not removed.
6. Close Firefox/TBB.
7. Observe that the temp-created file is not removed.
Firefox 28's Private Mode does not have this bug.
I observed this bug in TBB v2.x as well.
**Trac**:
**Username**: ericlawhttps://gitlab.torproject.org/legacy/trac/-/issues/11776Could not connect to tor control port2020-06-15T23:18:42ZTracCould not connect to tor control portI have tried a number of things as per Matt Pagan's advice.
Time is accurate
Have disabled firewall
Have disabled anti virus
Removed and reinstalled ~~TOR~~ Tor Browser~~~~
I always get the same message
could not connect to tor control...I have tried a number of things as per Matt Pagan's advice.
Time is accurate
Have disabled firewall
Have disabled anti virus
Removed and reinstalled ~~TOR~~ Tor Browser~~~~
I always get the same message
could not connect to tor control port
I use windows vista ~~and firefox~~
**Trac**:
**Username**: jim197https://gitlab.torproject.org/legacy/trac/-/issues/12426Make use of HeapEnableTerminationOnCorruption in Tor Browser on Windows2020-06-15T23:44:00ZGeorg KoppenMake use of HeapEnableTerminationOnCorruption in Tor Browser on WindowsThis function gets defined in ipc/chromium/src/base/process_util* but is only used in the test suite: https://mxr.mozilla.org/mozilla-esr24/source/ipc/chromium/src/base/test_suite.h. We should make more use of it in the code itself. See:...This function gets defined in ipc/chromium/src/base/process_util* but is only used in the test suite: https://mxr.mozilla.org/mozilla-esr24/source/ipc/chromium/src/base/test_suite.h. We should make more use of it in the code itself. See: https://blogs.msdn.com/b/oldnewthing/archive/2013/12/27/10484882.aspx for more information.https://gitlab.torproject.org/legacy/trac/-/issues/12427Investigate Virtual Table Verification (VTV) hardening for Tor Browser on Lin...2020-06-15T23:18:57ZGeorg KoppenInvestigate Virtual Table Verification (VTV) hardening for Tor Browser on Linux and WindowsVTV (see: https://gcc.gnu.org/wiki/vtv) is a hardening feature introduced in GCC 4.9.0 which might be usable for our Tor Browser builds for Linux and Windows as we are using GCC for (cross-)compiling. We should investigate that and fix p...VTV (see: https://gcc.gnu.org/wiki/vtv) is a hardening feature introduced in GCC 4.9.0 which might be usable for our Tor Browser builds for Linux and Windows as we are using GCC for (cross-)compiling. We should investigate that and fix possible roadblocks.https://gitlab.torproject.org/legacy/trac/-/issues/12672Tor log should be accessible while Tor Browser is starting up2020-06-13T17:43:02ZTracTor log should be accessible while Tor Browser is starting upSometimes users write to the Help Desk saying that their Tor Browsers do not manage to start. Since it does not start and stops in the initial loading "Tor Status" screen displaying "Connecting to the Tor Network", users are unable to gr...Sometimes users write to the Help Desk saying that their Tor Browsers do not manage to start. Since it does not start and stops in the initial loading "Tor Status" screen displaying "Connecting to the Tor Network", users are unable to grab a log to send to the Help Desk.
**Trac**:
**Username**: EnviteKathleen BradeKathleen Bradehttps://gitlab.torproject.org/legacy/trac/-/issues/12820Test+Recommend Tor Browser with MS EMET (Enhanced Mitigation Experience Toolkit)2020-06-15T23:19:36ZMike PerryTest+Recommend Tor Browser with MS EMET (Enhanced Mitigation Experience Toolkit)The Enhanced Mitigation Experience Tookit is a Microsoft tool for further hardening selected applications against exploitation. We should test it with Tor Browser to see if it impacts functionality in any way, and if not, we should consi...The Enhanced Mitigation Experience Tookit is a Microsoft tool for further hardening selected applications against exploitation. We should test it with Tor Browser to see if it impacts functionality in any way, and if not, we should consider recommending it somewhere prominently for our Windows users.
https://support.microsoft.com/kb/2458544https://gitlab.torproject.org/legacy/trac/-/issues/12926Make sure our linker gets used when compiling Tor Browser for Windows2020-06-15T23:19:45ZGeorg KoppenMake sure our linker gets used when compiling Tor Browser for Windows#12753 zeroed out the timestamp in the PE header but surprisingly not everywhere (e.g. not in the tor.exe). This might be due to the fact that our own linker is not used in these cases. See the hint in gitian-firefoy.yml
```
XXX: the pa...#12753 zeroed out the timestamp in the PE header but surprisingly not everywhere (e.g. not in the tor.exe). This might be due to the fact that our own linker is not used in these cases. See the hint in gitian-firefoy.yml
```
XXX: the path to ld is hardcoded in mingw..
```
which would explain why tor.exe and the mingw-w64 libs we build in gitian-utils.yml are affected.https://gitlab.torproject.org/legacy/trac/-/issues/13017Determine if AudioBuffers/OfflineAudioContext are a fingerprinting vector2020-06-15T23:19:56ZMike PerryDetermine if AudioBuffers/OfflineAudioContext are a fingerprinting vectorWebAudio allows you to write data to AudioBuffers and perform effects/manipulation/spectral analysis on them, and extract their contents.
If the underlying routines are OS supported, they may be fingerprintable. https://developer.mozill...WebAudio allows you to write data to AudioBuffers and perform effects/manipulation/spectral analysis on them, and extract their contents.
If the underlying routines are OS supported, they may be fingerprintable. https://developer.mozilla.org/en-US/docs/Web_Audio_APIArthur EdelsteinArthur Edelsteinhttps://gitlab.torproject.org/legacy/trac/-/issues/13419Fix cross-compiling ICU with mingw-w64 for Windows builds2020-06-15T23:34:37ZGeorg KoppenFix cross-compiling ICU with mingw-w64 for Windows buildsCross-compiling ICU with mingw-w64 is currently broken which is why we disable it. See: https://bugzilla.mozilla.org/show_bug.cgi?id=1019744#c19 for some details. Jacek does not plan to work on that one he told me.Cross-compiling ICU with mingw-w64 is currently broken which is why we disable it. See: https://bugzilla.mozilla.org/show_bug.cgi?id=1019744#c19 for some details. Jacek does not plan to work on that one he told me.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/legacy/trac/-/issues/13437Rounded inner window accidentally grows to non-rounded size of browser window...2020-06-15T23:21:16ZcypherpunksRounded inner window accidentally grows to non-rounded size of browser window on WindowsThere are problems with resizing on latest browser release.
When I click new identity and check panopticlick, it shows 1000x600. But if I go full screen and revert back, the results show 1004x632There are problems with resizing on latest browser release.
When I click new identity and check panopticlick, it shows 1000x600. But if I go full screen and revert back, the results show 1004x632https://gitlab.torproject.org/legacy/trac/-/issues/13893Torbrowser crashes on start when using MS EMET 5.x2020-06-15T23:38:22ZTracTorbrowser crashes on start when using MS EMET 5.xTrying to start the Tor Browser on Win7 x64 SP1 with MS EMET 5.1 installed and firefox.exe added to it leads to the following crash of firefox.exe:
EMET detected SimExecFlow mitigation and will close the application: firefox.exe
SimExe...Trying to start the Tor Browser on Win7 x64 SP1 with MS EMET 5.1 installed and firefox.exe added to it leads to the following crash of firefox.exe:
EMET detected SimExecFlow mitigation and will close the application: firefox.exe
SimExecFlow check failed:
Application : D:\Tor Browser\Browser\firefox.exe
User Name : XYZ\XYZ
Session ID : 1
PID : 0x1280 (4736)
TID : 0x12C8 (4808)
CodeAddress : 0x62B5EEF2
CodeStackPtr : 0x3CF190
CalledAddress : 0x77324AFF
API name : kernel32.VirtualProtectEx
StackPtr : 0x003CF130
FramePtr : 0x763298
IMHO it should be possible or even best practise to use Tor Browser together with EMET. Perhas a core developer can take a look at this. If you need more information, let me know.
**Trac**:
**Username**: Diapolohttps://gitlab.torproject.org/legacy/trac/-/issues/13972check.torproject.org doesn't support TLS 1.22020-06-13T17:13:29ZTraccheck.torproject.org doesn't support TLS 1.2I was checking check.torproject.org using SSLtest.
https://www.ssllabs.com/ssltest/analyze.html?d=check.torproject.org
According to Adam Langley from Google
"This seems like a good moment to reiterate that everything less than TLS 1.2 ...I was checking check.torproject.org using SSLtest.
https://www.ssllabs.com/ssltest/analyze.html?d=check.torproject.org
According to Adam Langley from Google
"This seems like a good moment to reiterate that everything less than TLS 1.2 with an AEAD cipher suite is cryptographically broken."
https://www.imperialviolet.org/2014/12/08/poodleagain.html
**Trac**:
**Username**: mkralArlo BreaultArlo Breaulthttps://gitlab.torproject.org/legacy/trac/-/issues/15775Add IPv4 Fallback Directory List to tor, active by default2020-06-13T14:51:37ZteorAdd IPv4 Fallback Directory List to tor, active by defaultweasel writes on tor-dev:
Tor has included a feature to fetch the initial consensus from nodes
other than the authorities for a while now. We just haven't shipped a
list of alternate locations for clients to go to yet.
Reasons why we ...weasel writes on tor-dev:
Tor has included a feature to fetch the initial consensus from nodes
other than the authorities for a while now. We just haven't shipped a
list of alternate locations for clients to go to yet.
Reasons why we might want to ship tor with a list of additional places
where clients can find the consensus is that it makes authority
reachability and BW less important.
At the last Tor dev meeting we came up with a list of arbitrary
requirements that nodes should meet to be included in this list.
We want them to have been around and using their current key, address,
and port for a while now (120 days), and have been running, a guard, and
a v2 directory mirror for most of that time.
I have written a script to come up with a list of notes that match our
criteria. It's currently at
https://www.palfrader.org/volatile/fallback-dir/get-fallback-dir-candidates
It currently produces
https://www.palfrader.org/volatile/2015-04-17-VjBkc8DWV8c/list
See https://lists.torproject.org/pipermail/tor-dev/2015-April/008674.html
This file current has 329 entries, and takes up approximately 32kB.
If we hard-coded it in the binary like the authorities, it would increase the binary size by approximately 2% on my platform.
Edit: nickm favours putting it in `torrc.defaults`
Edit 2: weasel notes `torrc.defaults` is for package maintainers. Putting it in a list of strings in the code. Much like the authorities.
Do we expect this in by 0.2.7?
Edit: Yes
Do we want to work on a signed file first (#15774)?
(A signed file needs a well-defined threat model and signature verification has to work without access to the authorities or fallback directories.)
Edit: No clear threat model, defer.Tor: 0.2.8.x-finalteorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/16010Get a working content process sandbox for Tor Browser on Windows2020-06-15T23:47:43ZGeorg KoppenGet a working content process sandbox for Tor Browser on WindowsWe are about to compile Tor Browser for Windows with `--disable-sandbox` as it breaks with mingw-w64 otherwise (https://bugzilla.mozilla.org/show_bug.cgi?id=1042426). One of the main problems is that SEH is not available in GCC mainly du...We are about to compile Tor Browser for Windows with `--disable-sandbox` as it breaks with mingw-w64 otherwise (https://bugzilla.mozilla.org/show_bug.cgi?id=1042426). One of the main problems is that SEH is not available in GCC mainly due to patent issues (See: https://gcc.gnu.org/wiki/WindowsGCCImprovements section Structured Exception Handling (SEH)). According to Jacek the patent expired but still there has no one written the proper code for GCC yet.
We might want to think about ways to get that fixed for us by third parties I guess.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/legacy/trac/-/issues/16072Stop using reCaptcha on all your services2020-06-13T16:49:44ZcypherpunksStop using reCaptcha on all your servicesbecause
1 reCaptha is unsolvable when you are using Tor
2 reCaptcha allows Google to track user's visitsbecause
1 reCaptha is unsolvable when you are using Tor
2 reCaptcha allows Google to track user's visitshttps://gitlab.torproject.org/legacy/trac/-/issues/16747Tor-browser downloads favicon twice (and over different circuits) on Windows2020-06-15T23:28:08ZcypherpunksTor-browser downloads favicon twice (and over different circuits) on WindowsWhen opening an image directly inside Tor-browser it ends up being downloaded twice.
Two HTTP GET requests get sent to the server.
The issue comes from the icon shown on the tabbar:
If I disable browser.chrome.favicons and browser.chrom...When opening an image directly inside Tor-browser it ends up being downloaded twice.
Two HTTP GET requests get sent to the server.
The issue comes from the icon shown on the tabbar:
If I disable browser.chrome.favicons and browser.chrome.site_icons then the double download does not happen.
Can this be prevented by for instance loading the tab icon from the cache?https://gitlab.torproject.org/legacy/trac/-/issues/16926Multiple OS: Tor Browser leaks domains to system DNS management.2020-06-15T23:29:12ZTracMultiple OS: Tor Browser leaks domains to system DNS management.Someone recently posted this bug:
https://trac.torproject.org/projects/tor/ticket/16813
Which describes what appeared to be a serious DNS leak from Tor to the Linux system’s DNS management, nscd.
But the same thing is happening on OS ...Someone recently posted this bug:
https://trac.torproject.org/projects/tor/ticket/16813
Which describes what appeared to be a serious DNS leak from Tor to the Linux system’s DNS management, nscd.
But the same thing is happening on OS X with mDNSResponder.
The following command: sudo killall -INFO mDNSResponder will dump the contents of the DNS cache to system.log.
And within that I found one site that has *only* been visited via Tor Browser.
I’m not sure why it was only one after a heavy Tor session, and subsequent attempts to repeat this have not reproduced the problem.
Now I’ve learned this isn’t new, others have commented the same in the past:
https://maymay.net/blog/2013/02/20/howto-use-tor-for-all-network-traffic-by-default-on-mac-os-x/comment-page-1/#comment-965581
https://maymay.net/blog/2013/02/20/howto-use-tor-for-all-network-traffic-by-default-on-mac-os-x/comment-page-1/#comment-995659
I actually tested recent Tor Browser versions quite thoroughly from time to time with tcpdump and inspecting the dump either by grepping for IP addresses other than the expected entry node or inspecting in Wireshark and have never seen a ‘live’ DNS leak from Tor yet.
But it’s difficult to tell from the mDNSResponder dump in system.log if mDNSResponder is sometimes trying to look up domains visited over Tor in clearnet.
The comments in the above 2 links believe that is the case and they recommend mDNSResponder has to be disabled before Tor use.
The entry of the mDNSResponder dump in system log was:
Aug 30 02:29:23 mymachine mDNSResponder[39]: 78 4252 -U- Addr 4 tor-only-visited-site.com Addr 123.123.123.123
Can we get some *urgent* clarification about how Tor Browser is handling this ?
Is it merely the case that the system DNS service has to have access to sites Tor is connecting to but isn’t actually doing any DNS lookups in the clear but they are just (sometimes?) ending up in its cache?
Or is it the case that if DNS look ups over Tor fail or stall they being passed to the system to ‘have a go’ ? Can we get some answers please, because the information is currently extremely vague.
Note I believe in more recent versions of OS X mDNSResponder has been replaced with a service called discoveryd, but I’m using not using these later versions.
Tor Browser version is the latest 5.02 OS X
**Trac**:
**Username**: DrMikeTwiddlehttps://gitlab.torproject.org/legacy/trac/-/issues/16978Minority of hostile dirauths can influence consensus in dangerous ways2020-06-13T14:48:46ZSebastian HahnMinority of hostile dirauths can influence consensus in dangerous waysWe like to claim that if a minority of dirauths is not honest, the worst they can do is manipulate the voting process in such a way that no consensus emerges but not that a consensus emerges that is (at least partially) dictated by the b...We like to claim that if a minority of dirauths is not honest, the worst they can do is manipulate the voting process in such a way that no consensus emerges but not that a consensus emerges that is (at least partially) dictated by the bad actors. Unfortunately, this isn't the case for the opt-in features. If a majority of the dirauths opting in to features such as bad exit voting, bandwidth measurements, or voting for a specific parameter want to influence these values in the consensus, they don't require a majority of total dirauths to do that. This might not be so much of an issue with less important features like Naming, but since badexit and bandwidth weight directly influences path selection on the client, these authorities that opt in to those features have considerably more power over the consensus than those that do not.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/17175Site is able to detect locale in some way2020-06-15T23:29:48ZcypherpunksSite is able to detect locale in some wayToday I tried to search Google using localized Tor Browser. And I was VERY SURPRISED to see localized search results (though the page was in English). Some time after that I was far more surprised to see the page being redirected to the ...Today I tried to search Google using localized Tor Browser. And I was VERY SURPRISED to see localized search results (though the page was in English). Some time after that I was far more surprised to see the page being redirected to the localized Google domain. I examined the headers using devtools and I haven't seen any signs of my locale in them. I examined the path, the exit node is not in my country. How could they detect it? This should be investigated and fixed.
I use TBB 5.0.3.
The settings are:
extensions.torbutton.spoof_language;en-us, en
extensions.torbutton.spoof_english;true
extensions.torbutton.spoof_locale;en-US
javascript.default_locale;en-US
intl.accept_languages;en-US, en
javascript.enabled;true
noscript.global;false
capability.policy.maonoscript.sites;about: about:addons about:blocked about:certerror about:config about:crashes about:home about:memory about:neterror about:plugins about:preferences about:privatebrowsing about:sessionrestore about:srcdoc about:support blob: chrome: mediasource: moz-safe-about: resource:https://gitlab.torproject.org/legacy/trac/-/issues/17193Don't print bridge IPs/fingerprints in WARN/NOTICE log messages2020-06-13T14:49:42ZIsis LovecruftDon't print bridge IPs/fingerprints in WARN/NOTICE log messagesBy default, we currently print out bridge IP:ports and fingerprints in tor's log messages at the notice and warn levels. Users often [copy+paste these logs to various public places](https://lists.torproject.org/pipermail/tor-talk/2015-Se...By default, we currently print out bridge IP:ports and fingerprints in tor's log messages at the notice and warn levels. Users often [copy+paste these logs to various public places](https://lists.torproject.org/pipermail/tor-talk/2015-September/039143.html) when trying to debug why their connection isn't working.
I understand that this is probably useful information to give to the support desk for debugging why tor isn't working… but would it be doable to have the support people ask, _"Hey could you add `SafeLogging 0` to your torrc?"_ or something?
I think the default should be to sanitise bridge IP:ports and fingerprints at these levels.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/17207Testing navigator.mimeTypes for known names can reveal info and increase fing...2020-06-15T23:33:00ZTracTesting navigator.mimeTypes for known names can reveal info and increase fingerprinting riskI gathered a list of MIME Types from IANA and other sources. Then explicitly used each type to check if navigator.mimeTypes[type] === undefined. I found that I could detect quite a few MIME Types in this way. Including some types that...I gathered a list of MIME Types from IANA and other sources. Then explicitly used each type to check if navigator.mimeTypes[type] === undefined. I found that I could detect quite a few MIME Types in this way. Including some types that are related to specific application programs and/or peripheral devices.
I maxed the security slider, which disabled Javascript by default and broke the test script. However, after I whitelisted the test script I was able to achieve the same results.
I was testing Tor Browser 5.0.3 for Windows.
**Trac**:
**Username**: TemporaryNickArthur EdelsteinArthur Edelsteinhttps://gitlab.torproject.org/legacy/trac/-/issues/17217Change clients to automatically use IPv6 if they can bootstrap over it2020-06-13T14:49:46ZteorChange clients to automatically use IPv6 if they can bootstrap over itTor currently defaults to avoiding IPv6 directories and ORPorts.
When #8374 and #4483 are implemented, we should change this default, especially for those clients that can bootstrap successfully over IPv6.
I suggest we add an "auto" opt...Tor currently defaults to avoiding IPv6 directories and ORPorts.
When #8374 and #4483 are implemented, we should change this default, especially for those clients that can bootstrap successfully over IPv6.
I suggest we add an "auto" option, and make it the default. It would mean that the client uses whichever IP version it bootstrapped over.
```
ClientUseIPv6 0
ClientPreferIPv6ORPort 0
```Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/17218Move most of "circuit_mark_for_close" into "circuit_free" or "circuit_close_a...2020-06-13T14:49:47ZNick MathewsonMove most of "circuit_mark_for_close" into "circuit_free" or "circuit_close_all_marked".The function "circuit_mark_for_close()" calls a few other functions (notably circuit_build_failed() and rend_client_report_intro_point_failure()) that call into the blob. If we pull it out, we would chop the remaining blob in half...The function "circuit_mark_for_close()" calls a few other functions (notably circuit_build_failed() and rend_client_report_intro_point_failure()) that call into the blob. If we pull it out, we would chop the remaining blob in half.
We should use a system similar to the one we use for closeable connections where we put closeable circuits on a list, rather than iterating over the entire circuit list.
Doing this would remove more than half of the functions currently in the blob as currently measured. (!)Tor: 0.2.8.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/17321Index to better support downloaders2020-06-13T17:50:14ZDamian JohnsonIndex to better support downloadersHi Karsten, as discussed at the dev meeting it would be sweeeeeet for Stem to have a CollecTorDownloader class that supports getting and processing descriptors from CollecTor.
Presently you read and process the Apache index html, but it...Hi Karsten, as discussed at the dev meeting it would be sweeeeeet for Stem to have a CollecTorDownloader class that supports getting and processing descriptors from CollecTor.
Presently you read and process the Apache index html, but it would it could be a lot nicer to have a machine readable index.json file instead. This is the ticket for it.
To support future expansion it would be nice to be able to include additional metadata, so I propose a 'contents' hash, such as...
```
https://collector.torproject.org/recent/index.json
{
'resource': 'https://collector.torproject.org/recent/index.json',
'contents': [
{
'name': 'bridge-descriptors',
'type': 'directory',
'last_modified': '31-May-2014 09:49', # or a unix timestam?
'url': 'https://collector.torproject.org/recent/bridge-descriptors/'
},
{
'name': 'exit-lists',
'type': 'directory',
'last_modified': '11-Oct-2015 15:02',
'url': 'https://collector.torproject.org/recent/exit-lists/'
},
{
'name': 'example-file.txt',
'type': 'file',
'last_modified': '31-May-2014 09:50',
'size': 42901,
'url': 'https://collector.torproject.org/recent/example-file.txt'
}
]
}
```Karsten LoesingKarsten Loesinghttps://gitlab.torproject.org/legacy/trac/-/issues/17346Rename Tor Messenger on Git and Trac2020-06-13T16:50:16ZSukhbir SinghRename Tor Messenger on Git and Trac```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
As part of the rebranding, Tor Messenger is now called Unnamed Messenger. We would like to rename `tor-messenger-build.git` to `unnamed-messenger-build.git` and same goes for the trac ...```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
As part of the rebranding, Tor Messenger is now called Unnamed Messenger. We would like to rename `tor-messenger-build.git` to `unnamed-messenger-build.git` and same goes for the trac component (`Tor Messenger` to `Unnamed Messenger`).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJWHXUPAAoJEGiHk1qyl7ORwnQP/iV3IZcOLz6XDJXz+rucYwWW
/Vr5W8rKFeOFPoLn5qqm2NWDATNS2S4d3oY4hemedhWM4DSWn14afkimWjWM2mJ1
/sYZSwQVf9nAm3hv5I9Po44OFSBPqmggt3/ng8yQ7FmsB4wz0vkoEaFaXBGWOtfv
vkIMRqcHMDrtzxhfOLJtj2WTD/BhZdD0pJaAf1NVylFitPYzcST+JFizat1C1q5s
MK/0IWISGkI5Ey4vo1WsA/VKghHg1CzTX9xUt30VY/+xj9rjMXgmnJd9+gnweoWt
AovPBLVHwhaBl8h9syvyrpOTGOCf4Ta9QGxxQ+9D4XTcqMYJQWhfYrCOLFM+MgtF
A6299/RrsHwLZkSmm+NS7sVwsTcYrRHGYfyVu+j3ng2HKr6dKCF2K+MbMo+ReGky
IQxE9oTGlwLIPbY6oqjyrtYxv24ekBTCb7SPPUeTjOyahDhBVHGRckh7Nxc/5oMz
Dsj+nhLhEzDQoGteKwUFsSnSkA0Hfz/tVo1jRwdbB3aaLhqEIWrxH1kM/Dqwn7ei
I8UxHweNY54bgj8e74P1pBSflJ3gK5xII0dinSVcQzXD2D8PbV192JBIKXcrYL6K
VG9wp3/NTGgbqNdM/RpfkyjAl87Rw/j/Km7vzwLS/qaj3DZPOSiJq5inOal6loEA
8WDSkZ0T5Jx7afbkv+MF
=s5RW
-----END PGP SIGNATURE-----
```https://gitlab.torproject.org/legacy/trac/-/issues/17350Anycast Resolution in OONI measurements2018-07-03T22:32:19ZwillscottAnycast Resolution in OONI measurementsCurrently, OONI measurements are not anycast aware. When a domain resolves to an IP which is served by multiple servers depending on geographic location, we have no way to determine which actual server the client attempts to contact, or ...Currently, OONI measurements are not anycast aware. When a domain resolves to an IP which is served by multiple servers depending on geographic location, we have no way to determine which actual server the client attempts to contact, or where it is.
This is a broad issue, and there are several smaller components that need to be addressed to do a reasonable job of resolution.
First, we need to know which IPs are anycasting, then we need to know the locations of the different servers, and finally we need to know which clients are routed to which servers.Arturo FilastòArturo Filastòhttps://gitlab.torproject.org/legacy/trac/-/issues/17367Swap files can contain evidence of browsing history2020-06-15T23:30:27ZArthur EdelsteinSwap files can contain evidence of browsing historyTwo forensic reports describe extracting Tor Browser browsing history from a Windows pagefile.sys and hiberfil.sys:
See
http://computerforensicsblog.champlain.edu/wp-content/uploads/2014/06/One-User-Multiple-Devices-Cross-Platform-Recov...Two forensic reports describe extracting Tor Browser browsing history from a Windows pagefile.sys and hiberfil.sys:
See
http://computerforensicsblog.champlain.edu/wp-content/uploads/2014/06/One-User-Multiple-Devices-Cross-Platform-Recovery-and-Analysis...-Saliba-Landry-5-20-2014.pdf#33
and
https://web.archive.org/web/20160403075329/http://dfrws.org/2015eu/proceedings/DFRWS-EU-2015-short-presentation-1.pdf#16
Is there any way we can programmatically clean up the pagefile on New Identity and/or browser exit? What about OS X and Linux?https://gitlab.torproject.org/legacy/trac/-/issues/17369The RC4 cipher flags in TBB must be set to "false" by default2020-06-15T23:42:45ZTracThe RC4 cipher flags in TBB must be set to "false" by defaultRelated to the obsolete/broken RC4 cipher, the TBB v5.0.3 about:config -> RC4 has 5 flags set to "true" by default
security.ssl3.ecdhe_ecdsa_rc4_128_sha;true
security.ssl3.ecdhe_rsa_rc4_128_sha;true
security.ssl3.rsa_rc4_128_md5;true
se...Related to the obsolete/broken RC4 cipher, the TBB v5.0.3 about:config -> RC4 has 5 flags set to "true" by default
security.ssl3.ecdhe_ecdsa_rc4_128_sha;true
security.ssl3.ecdhe_rsa_rc4_128_sha;true
security.ssl3.rsa_rc4_128_md5;true
security.ssl3.rsa_rc4_128_sha;true
security.tls.unrestricted_rc4_fallback;true
Since the RC4 was proved insecure and obsolete, the TBB must avoid using this by default
https://community.qualys.com/blogs/securitylabs/2015/05/21/ssl-labs-117-obsolete-crypto-rc4-and-logjam
**Trac**:
**Username**: TORqueshttps://gitlab.torproject.org/legacy/trac/-/issues/17383rsync hang in Gitian bundling step2020-06-15T23:30:40ZGeorg Koppenrsync hang in Gitian bundling stepln5 just got his nightly build to hang in the 64 bit Linux bundling step. The reason is similar to #10153: `libfaketime` is interfering with the inner rsync workings in a bad way. Might be easiest to just copy and paste the solution that...ln5 just got his nightly build to hang in the 64 bit Linux bundling step. The reason is similar to #10153: `libfaketime` is interfering with the inner rsync workings in a bad way. Might be easiest to just copy and paste the solution that excludes `rsync` from `libfaketime`'s reach. This might be safer than not having libfaketime active when running `makexpi.sh`.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/legacy/trac/-/issues/17395Crash on OS X 10.11 Tor Browser 5.0.32020-06-15T23:30:59ZTracCrash on OS X 10.11 Tor Browser 5.0.3Process: firefox [34643]
Path: /Applications/TorBrowser.app/Contents/MacOS/firefox
Identifier: org.mozilla.tor browser
Version: 5.0.3 (3800.1.1)
Code Type: X86-64 (Nativ...Process: firefox [34643]
Path: /Applications/TorBrowser.app/Contents/MacOS/firefox
Identifier: org.mozilla.tor browser
Version: 5.0.3 (3800.1.1)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: firefox [34643]
User ID: 501
Date/Time: 2015-10-20 18:56:06.886 -0700
OS Version: Mac OS X 10.11 (15A284)
Report Version: 11
Anonymous UUID: 84F8AED3-D01F-AB11-7207-1367D32CDAF2
Sleep/Wake UUID: 285F790C-336A-4FC9-B421-DC28EC168ADA
Time Awake Since Boot: 470000 seconds
Time Since Wake: 17000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000065e5e5e5e5f8
Exception Note: EXC_CORPSE_NOTIFY
VM Regions Near 0x65e5e5e5e5f8:
VM_ALLOCATE 000000018a900000-000000018ee00000 [ 69.0M] rw-/rwx SM=PRV
-->
STACK GUARD 0000700000000000-0000700000001000 [ 4K] ---/rwx SM=NUL stack guard for thread 47
Application Specific Information:
objc_msgSend() selector name: hash
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff8d7f3d5d objc_msgSend + 29
1 com.apple.Foundation 0x00007fff9423a7e4 -[NSConcreteMapTable objectForKey:] + 42
2 com.apple.UIFoundation 0x00007fff9cbf289d +[__NSFontTypefaceInfo typefaceInfoForPostscriptName:options:] + 155
3 com.apple.UIFoundation 0x00007fff9cbf9677 __NSGetMetaFontInstance + 1099
4 XUL 0x000000010237c615 0x101bd5000 + 8025621
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff9edf40a2 kevent_qos + 10
1 libdispatch.dylib 0x00007fff9e7431ad _dispatch_mgr_invoke + 216
2 libdispatch.dylib 0x00007fff9e742e15 _dispatch_mgr_thread + 52
Thread 2:: Gecko_IOThread
0 libsystem_kernel.dylib 0x00007fff9edf4072 kevent + 10
1 XUL 0x0000000101e404f1 0x101bd5000 + 2536689
Thread 3:: Socket Thread
0 libsystem_kernel.dylib 0x00007fff9edf3222 __select + 10
1 libnss3.dylib 0x0000000101aeb725 poll + 485
Thread 4:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 5:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 6:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 7:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 8:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 9:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 10:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 11:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 12:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 13:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 14:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 15:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 16:
0 libsystem_kernel.dylib 0x00007fff9ededc96 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff9eded0d7 mach_msg + 55
2 XUL 0x0000000103d5b620 0x101bd5000 + 35153440
Thread 17:: JS Watchdog
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 18:: Hang Monitor
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 19:: Timer
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe769 PR_WaitCondVar + 249
Thread 20:: Cache2 I/O
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 21:
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 22:: Cert Verify
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 23:: mozStorage #1
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 24:: Proxy R~olution
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 25:: RunProcess
0 libsystem_kernel.dylib 0x00007fff9edf372a __wait4 + 10
1 XUL 0x0000000101c61eae 0x101bd5000 + 577198
Thread 26:: IPDL Background
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 27:: ImageIO
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 28:: Compositor
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 XUL 0x0000000101e423c8 0x101bd5000 + 2544584
3 ??? 0x8000000000000000 0 + 9223372036854775808
Thread 29:: ImageBridgeChild
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 XUL 0x0000000101e423c8 0x101bd5000 + 2544584
3 ??? 0x8000000000000000 0 + 9223372036854775808
Thread 30:: ImageDecoder #1
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afeddf PR_Wait + 303
Thread 31:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x00007fff9ededc96 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff9eded0d7 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff8eff2024 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff8eff14ec __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff8eff0d38 CFRunLoopRunSpecific + 296
5 com.apple.AppKit 0x00007fff9106deed _NSEventThread + 149
6 libsystem_pthread.dylib 0x00007fff9a8979b1 _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff9a89792e _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff9a895385 thread_start + 13
Thread 32:: DOM Worker
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 33:
0 libsystem_kernel.dylib 0x00007fff9ededc96 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff9eded0d7 mach_msg + 55
2 XUL 0x0000000103d5ab05 0x101bd5000 + 35150597
Thread 34:: ImageDecoder #2
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afeddf PR_Wait + 303
Thread 35:: ImageDecoder #3
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afeddf PR_Wait + 303
Thread 36:: ImageDecoder #4
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afeddf PR_Wait + 303
Thread 37:: MediaManager
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 38:: Cache I/O
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 39:: mozStorage #2
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 40:: mozStorage #3
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 41:: localStorage DB
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 42:: mozStorage #4
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 43:: URL Classifier
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 44:: mozStorage #5
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 45:: mozStorage #6
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 46:: mozStorage #7
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 47:: HTML5 Parser
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 48:: Image Scaler
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 49:
0 libsystem_kernel.dylib 0x00007fff9edf378a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff9a89758c _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff9a895375 start_wqthread + 13
Thread 50:
0 libsystem_kernel.dylib 0x00007fff9edf378a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff9a89758c _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff9a895375 start_wqthread + 13
Thread 51:
0 libsystem_kernel.dylib 0x00007fff9edf378a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff9a89758c _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff9a895375 start_wqthread + 13
Thread 52:
0 libsystem_kernel.dylib 0x00007fff9edf378a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff9a89758c _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff9a895375 start_wqthread + 13
Thread 53:
0 libsystem_kernel.dylib 0x00007fff9edf378a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff9a89758c _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff9a895375 start_wqthread + 13
Thread 54:
0 libsystem_kernel.dylib 0x00007fff9edf378a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff9a89758c _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff9a895375 start_wqthread + 13
Thread 55:
0 libsystem_kernel.dylib 0x00007fff9edf378a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff9a89758c _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff9a895375 start_wqthread + 13
Thread 56:
0 libsystem_kernel.dylib 0x00007fff9edf378a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff9a89758c _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff9a895375 start_wqthread + 13
Thread 57:: DOM Worker
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 58:: mozStorage #8
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
Thread 59:
0 libsystem_kernel.dylib 0x00007fff9ededc96 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff9eded0d7 mach_msg + 55
2 XUL 0x0000000103d5ab05 0x101bd5000 + 35150597
Thread 60:
0 libsystem_kernel.dylib 0x00007fff9edf378a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff9a89758c _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff9a895375 start_wqthread + 13
Thread 61:: StreamTrans #12
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afeddf PR_Wait + 303
Thread 62:: SSL Cert #5
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afeddf PR_Wait + 303
Thread 63:: SSL Cert #6
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afeddf PR_Wait + 303
Thread 64:: SSL Cert #7
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afeddf PR_Wait + 303
Thread 65:: SSL Cert #8
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afeddf PR_Wait + 303
Thread 66:: DOM Worker
0 libsystem_kernel.dylib 0x00007fff9edf2f5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9a89873d _pthread_cond_wait + 767
2 libnss3.dylib 0x0000000101afe6d7 PR_WaitCondVar + 103
Thread 67:
0 libsystem_kernel.dylib 0x00007fff9ededc96 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff9eded0d7 mach_msg + 55
2 XUL 0x0000000103d5ab05 0x101bd5000 + 35150597
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000008 rbx: 0x00000001018ad620 rcx: 0x0000000000000000 rdx: 0x00007fff5fbfb6b0
rdi: 0x00000001018ad620 rsi: 0x00007fff8f3c7eb0 rbp: 0x00007fff5fbfb6a0 rsp: 0x00007fff5fbfb658
r8: 0x0000000000000017 r9: 0x0000000000000000 r10: 0x00007fff8f3c7eb0 r11: 0x000065e5e5e5e5e0
r12: 0x7d007ce67f862cf4 r13: 0x0000000000000000 r14: 0x00007fff7e4e40a8 r15: 0x000000010c131b40
rip: 0x00007fff8d7f3d5d rfl: 0x0000000000010202 cr2: 0x000065e5e5e5e5f8
Logical CPU: 4
Error Code: 0x00000004
Trap Number: 14
Binary Images:
0x100000000 - 0x100002ff7 +org.mozilla.tor browser (5.0.3 - 3800.1.1) <570D3E4C-DAE8-32E0-95E6-AB2715305522> /Applications/TorBrowser.app/Contents/MacOS/firefox
0x100005000 - 0x10001cff7 +libmozglue.dylib (1) <78CED24D-C806-3A6E-B51F-5C120108F51C> /Applications/TorBrowser.app/Contents/MacOS/libmozglue.dylib
0x100083000 - 0x100083fff +libmozalloc.dylib (1) <1AD23752-D412-33B7-87C7-43D4E933958C> /Applications/TorBrowser.app/Contents/MacOS/libmozalloc.dylib
0x1000ad000 - 0x1000b4fff +libbrowsercomps.dylib (???) <2E478AAA-05BA-3191-BCBE-66CFACED2987> /Applications/TorBrowser.app/Contents/Resources/browser/components/libbrowsercomps.dylib
0x101900000 - 0x101b6dff7 +libnss3.dylib (1) <B61C63E4-5007-3313-82D5-17CFE7B40D54> /Applications/TorBrowser.app/Contents/MacOS/libnss3.dylib
0x101bd5000 - 0x1057d3f07 +XUL (1) <3246A973-0652-3B39-81FE-7ED9FC2C5756> /Applications/TorBrowser.app/Contents/MacOS/XUL
0x1087fd000 - 0x1087fdfe7 +cl_kernels (???) <260290A4-D289-4E31-BEFA-70EA0C103939> cl_kernels
0x109a67000 - 0x109aa0fff +libsoftokn3.dylib (1) <F133FF99-2CEB-3BAD-BBF8-6AA50330D155> /Applications/TorBrowser.app/Contents/MacOS/libsoftokn3.dylib
0x10b832000 - 0x10b898ff7 +libfreebl3.dylib (1) <112FAFC9-451A-3754-B8A7-FD505E649D59> /Applications/TorBrowser.app/Contents/MacOS/libfreebl3.dylib
0x10bc42000 - 0x10bca2fff +libnssckbi.dylib (???) <D507092C-1073-372C-9EC1-6175ABD162EA> /Applications/TorBrowser.app/Contents/MacOS/libnssckbi.dylib
0x117f00000 - 0x11818eff3 com.apple.RawCamera.bundle (6.17 - 825) <EFF00605-B354-3F94-B4D0-1A14B08482FE> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
0x7fff60b7b000 - 0x7fff60bb1f5f dyld (360.14) <DF977301-4A63-32ED-9939-1EE3122D18D4> /usr/lib/dyld
0x7fff8ba21000 - 0x7fff8ba3dff7 libextension.dylib (78) <3A674BC1-8D7E-3A62-80EF-F950B02CB0FF> /usr/lib/libextension.dylib
0x7fff8ba3e000 - 0x7fff8ba91ff7 libc++.1.dylib (120.1) <54190E1B-EE49-3D6D-AC29-2813D7380BA5> /usr/lib/libc++.1.dylib
0x7fff8ba92000 - 0x7fff8bafeff7 com.apple.contacts.Contacts (1.0 - 2137) <3503806B-F315-3869-88FD-FFF8D5C10973> /System/Library/Frameworks/Contacts.framework/Versions/A/Contacts
0x7fff8bb65000 - 0x7fff8bb89fff libJPEG.dylib (1432) <69E090BE-7139-35B8-A621-BBE5CE2DB085> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x7fff8bedf000 - 0x7fff8bf82fff com.apple.Bluetooth (4.4.0 - 4.4.0f4) <DA1727B1-03EE-32BE-922E-43F06C498AFF> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
0x7fff8c6dd000 - 0x7fff8c6e4ff7 libcompiler_rt.dylib (62) <253B36E5-572D-377D-AE99-A02CE32590E5> /usr/lib/system/libcompiler_rt.dylib
0x7fff8c712000 - 0x7fff8c859fff com.apple.coreui (2.1 - 362) <1F30C006-9058-3B39-9DC3-594FDB108174> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x7fff8c861000 - 0x7fff8c862ff3 com.apple.print.framework.Print (10.0 - 266) <F13A0609-793A-3A43-A961-AAFC81AC8FDA> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
0x7fff8c8dd000 - 0x7fff8c904fff com.apple.shortcut (2.16 - 93) <F6E559D9-40BE-3CC9-BB16-E71300C77F8A> /System/Library/PrivateFrameworks/Shortcut.framework/Versions/A/Shortcut
0x7fff8c905000 - 0x7fff8c913fff com.apple.IntlPreferences (2.0 - 192) <5DE7D4D8-6E30-3AD2-B2BB-1E5475794768> /System/Library/PrivateFrameworks/IntlPreferences.framework/Versions/A/IntlPreferences
0x7fff8c971000 - 0x7fff8c979fff com.apple.AppleSRP (5.0 - 1) <8DBB11A2-150A-3E70-8B83-DDEDAB15E2C3> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP
0x7fff8c99b000 - 0x7fff8c9bffff com.apple.MultitouchSupport.framework (304.9 - 304.9) <650FA404-DC2C-365E-8373-218F1D765D35> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
0x7fff8c9c0000 - 0x7fff8c9eeff7 com.apple.DictionaryServices (1.2 - 250) <94678AC8-41FF-3D2E-A35E-D83AD18D7A78> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
0x7fff8c9ff000 - 0x7fff8ca66fff com.apple.framework.CoreWiFi (11.0 - 1100.19) <537EFC2F-3A23-36D7-9320-8834D51EB243> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi
0x7fff8ca81000 - 0x7fff8cb90fe7 libvDSP.dylib (563.3) <837D67E4-AA5D-3273-9CA5-EB42C3872E1B> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
0x7fff8cecf000 - 0x7fff8cefbfff com.apple.framework.SystemAdministration (1.0 - 1.0) <F17C889A-632F-3946-87F3-B797C5F1ED75> /System/Library/PrivateFrameworks/SystemAdministration.framework/Versions/A/SystemAdministration
0x7fff8cefc000 - 0x7fff8cf13fff libmarisa.dylib (4) <4D3AE55B-CE77-364F-B8DE-C95CAA48B291> /usr/lib/libmarisa.dylib
0x7fff8cf14000 - 0x7fff8cf38fff com.apple.quartzfilters (1.10.0 - 1.10.0) <B25F42F6-2548-39A8-9A9E-35331FD813EB> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzFilters.framework/Versions/A/QuartzFilters
0x7fff8cf39000 - 0x7fff8cf42ff3 com.apple.CommonAuth (4.0 - 2.0) <6EF43A6E-C071-36A3-8B94-694AC6BEF6D3> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
0x7fff8d1de000 - 0x7fff8d215ff7 com.apple.LDAPFramework (2.4.28 - 194.5) <207E4A14-E3CC-3658-ABAF-B5CAEC9ED1EB> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
0x7fff8d3ae000 - 0x7fff8d3ddfc3 libsystem_m.dylib (3105) <07D50372-30ED-3B03-9FA0-0662BF8F0098> /usr/lib/system/libsystem_m.dylib
0x7fff8d3de000 - 0x7fff8d4c5ff7 libcrypto.0.9.8.dylib (59) <7C4E5457-B66C-39CA-BC0E-15CA6C051FC0> /usr/lib/libcrypto.0.9.8.dylib
0x7fff8d4ca000 - 0x7fff8d4d8ff7 libbz2.1.0.dylib (38) <99C5121D-8147-3B51-8D79-66245C863338> /usr/lib/libbz2.1.0.dylib
0x7fff8d4d9000 - 0x7fff8d4dcffb libScreenReader.dylib (425.4) <1DCA43B7-C1BA-3A17-B69D-6F0491F648C0> /usr/lib/libScreenReader.dylib
0x7fff8d4dd000 - 0x7fff8d4defff libsystem_secinit.dylib (20) <932ED582-E80F-39DA-B0FA-F1BC5F1AD2F8> /usr/lib/system/libsystem_secinit.dylib
0x7fff8d4df000 - 0x7fff8d4e3fff com.apple.LoginUICore (3.1 - 3.1) <6DCEED7A-529B-3AFD-8F83-97A40B56E4D9> /System/Library/PrivateFrameworks/LoginUIKit.framework/Versions/A/Frameworks/LoginUICore.framework/Versions/A/LoginUICore
0x7fff8d4e4000 - 0x7fff8d50bfff com.apple.ChunkingLibrary (167 - 167) <C22F5038-7354-330F-8F38-36F187E6A4B1> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary
0x7fff8d560000 - 0x7fff8d6c7fff libBLAS.dylib (1159) <35ADE4D4-391A-30C2-9D38-388F543EA4BA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x7fff8d72f000 - 0x7fff8d736ff7 com.apple.phonenumbers (1.1.1 - 105) <49696A1F-83FC-3BE8-A7E8-F0F4EAA326BB> /System/Library/PrivateFrameworks/PhoneNumbers.framework/Versions/A/PhoneNumbers
0x7fff8d748000 - 0x7fff8d779ff7 libtidy.A.dylib (15.17) <917B7716-5060-3755-A1BA-435DAC06E778> /usr/lib/libtidy.A.dylib
0x7fff8d7c1000 - 0x7fff8d7d4fff com.apple.CoreBluetooth (1.0 - 1) <A63B8FB0-F8B3-368D-B482-733FF0373610> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
0x7fff8d7ed000 - 0x7fff8db506d7 libobjc.A.dylib (680) <7C5FAD04-2C01-3ED6-AA40-78925C12A456> /usr/lib/libobjc.A.dylib
0x7fff8db51000 - 0x7fff8dc3cff7 com.apple.QuickLookUIFramework (5.0 - 696.1) <921959F6-96C2-3814-8D20-0E761AB51199> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/QuickLookUI
0x7fff8dc3d000 - 0x7fff8dc3eff7 libodfde.dylib (23) <B2194A77-3D29-3CE2-9D96-F8986A198980> /usr/lib/libodfde.dylib
0x7fff8dc42000 - 0x7fff8dc5efff com.apple.GenerationalStorage (2.0 - 239) <05652CAD-E7F5-3225-929D-E13F241FBA41> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage
0x7fff8dc84000 - 0x7fff8dd33fff com.apple.cloudkit.CloudKit (480 - 480) <2507C1D3-733F-394A-9ADC-FF8FAD7D21B9> /System/Library/Frameworks/CloudKit.framework/Versions/A/CloudKit
0x7fff8dd44000 - 0x7fff8dd47ff7 com.apple.AppleSystemInfo (3.1.5 - 3.1.5) <E4643432-0DF2-3CD3-9F63-3A7665B25838> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo
0x7fff8dd48000 - 0x7fff8dd71fff libxpc.dylib (755.1.19) <3E09C275-A33B-357A-B0AB-A2DDF88EC9D5> /usr/lib/system/libxpc.dylib
0x7fff8e05b000 - 0x7fff8e06cff7 libsystem_trace.dylib (200) <E26A91EA-AD67-3FA2-A3B6-79A93DCC716E> /usr/lib/system/libsystem_trace.dylib
0x7fff8e193000 - 0x7fff8e1bcfff libc++abi.dylib (125) <F5027B46-1801-344D-BD51-2E6D188C8900> /usr/lib/libc++abi.dylib
0x7fff8e1bd000 - 0x7fff8e1bffff com.apple.EFILogin (2.0 - 2) <1FF63331-0B4A-385D-AC44-7AE665947553> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin
0x7fff8e1de000 - 0x7fff8e1fdff7 com.apple.contacts.vCard (1.0 - 2137) <74FA0133-CFBB-3055-B429-AF2D13B24D7D> /System/Library/PrivateFrameworks/vCard.framework/Versions/A/vCard
0x7fff8e279000 - 0x7fff8e2a4ff7 com.apple.AddressBook.ContactsFoundation (8.0 - 2137) <082A84FD-0076-3129-8193-2BCB0EAD15E2> /System/Library/PrivateFrameworks/ContactsFoundation.framework/Versions/A/ContactsFoundation
0x7fff8e2e5000 - 0x7fff8e429ff7 com.apple.QTKit (7.7.3 - 2937) <C04A69AB-93F9-3BB4-BF56-1CD408183CE7> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
0x7fff8e42a000 - 0x7fff8e42cff7 com.apple.SafariServices.framework (11601 - 11601.1.56) <AE587153-A7C4-39CB-9755-CF3B64402B3A> /System/Library/PrivateFrameworks/SafariServices.framework/Versions/A/SafariServices
0x7fff8e42d000 - 0x7fff8e45dff3 com.apple.CoreAVCHD (5.8.0 - 5800.4.2) <56AA41E6-2F60-31D8-B506-2D4A5C341C77> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD
0x7fff8e45e000 - 0x7fff8e4c1ff3 libAVFAudio.dylib (161) <1E0384CE-FF8D-36EE-8A28-50CD673D3109> /System/Library/Frameworks/AVFoundation.framework/Versions/A/Resources/libAVFAudio.dylib
0x7fff8e4c2000 - 0x7fff8e4c3ffb libremovefile.dylib (41) <C7CFF5F2-AFFB-3C8D-BDB4-D66D50E657C0> /usr/lib/system/libremovefile.dylib
0x7fff8e4c4000 - 0x7fff8e551fe7 libsystem_c.dylib (1081.1.3) <A60CE86D-1FF3-32AD-A672-C7597F884529> /usr/lib/system/libsystem_c.dylib
0x7fff8e599000 - 0x7fff8e59cfff com.apple.Mangrove (1.0 - 1) <7CA6F485-F7A5-301C-9F14-4C667EF8B2F3> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove
0x7fff8e59d000 - 0x7fff8e5effff com.apple.AppleVAFramework (5.0.31 - 5.0.31) <F0CFD860-FA5E-3BD5-80FA-12C0B4CF620D> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
0x7fff8e6ae000 - 0x7fff8e6d0ff7 com.apple.framework.familycontrols (4.1 - 410) <941D3CE9-826F-38C9-A553-6F44435ADFF6> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyControls
0x7fff8e6d1000 - 0x7fff8e6dafff com.apple.icloud.FindMyDevice (1.0 - 1) <28CE764F-4C4C-3A75-B7AE-EDBC7A189E82> /System/Library/PrivateFrameworks/FindMyDevice.framework/Versions/A/FindMyDevice
0x7fff8eac8000 - 0x7fff8ead6fff com.apple.opengl (12.0.34 - 12.0.34) <7D63C884-AF3D-3167-ABCE-F7EEBDF9762B> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x7fff8eb8d000 - 0x7fff8eb99fff com.apple.speech.synthesis.framework (5.4.12 - 5.4.12) <8D8F331E-21D2-3B7E-B977-3EB1D9E44D5B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x7fff8eb9a000 - 0x7fff8eba2fff libsystem_networkextension.dylib (384.1.2) <4736FCC5-9DBA-31F4-AAC8-CD0A177CF502> /usr/lib/system/libsystem_networkextension.dylib
0x7fff8eba3000 - 0x7fff8ebbcffb com.apple.openscripting (1.7 - 169) <6AA25650-8900-33C6-AD49-D0543DB27C16> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
0x7fff8ebbd000 - 0x7fff8ebc8fff libcsfde.dylib (517) <83340980-0FC2-33DC-B98B-562C4842568E> /usr/lib/libcsfde.dylib
0x7fff8ebd7000 - 0x7fff8ebebfff com.apple.CoreDuetDaemonProtocol (1.0 - 1) <EE4B9BE1-24CB-3A9A-97B1-21594C243EFF> /System/Library/PrivateFrameworks/CoreDuetDaemonProtocol.framework/Versions/A/CoreDuetDaemonProtocol
0x7fff8ecb5000 - 0x7fff8ecb8ff7 com.apple.help (1.3.3 - 46) <AA185754-DEEB-3091-9301-7B23C4D36818> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
0x7fff8eef2000 - 0x7fff8eef2fff libOpenScriptingUtil.dylib (169) <5C4A51D4-09A9-3209-8E57-15F112725CC4> /usr/lib/libOpenScriptingUtil.dylib
0x7fff8ef68000 - 0x7fff8f3dcff7 com.apple.CoreFoundation (6.9 - 1253) <A8A44D66-A3B2-3B5D-B75B-EC2DC968F4BD> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff8f3dd000 - 0x7fff8f3ddfff com.apple.Accelerate.vecLib (3.10 - vecLib 3.10) <4720E500-E247-3002-9672-EE2336D7679A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
0x7fff8f3de000 - 0x7fff8f44aff7 libType1Scaler.dylib (116) <0B5A89AB-A4EE-31FD-BFB7-456B7637DAAB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libType1Scaler.dylib
0x7fff8f44b000 - 0x7fff8f500fff com.apple.CoreDuet (1.0 - 1) <58D04404-6DD3-312F-A334-D1E89686B227> /System/Library/PrivateFrameworks/CoreDuet.framework/Versions/A/CoreDuet
0x7fff8f501000 - 0x7fff8f51afff com.apple.CFOpenDirectory (10.11 - 194) <64C52603-1947-3350-819E-3A45F9036036> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
0x7fff8f51b000 - 0x7fff8f810ff3 com.apple.HIToolbox (2.1.1 - 806) <510697D0-2F92-3256-B587-AD11DF988430> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x7fff8f811000 - 0x7fff8fc3ffff com.apple.vision.FaceCore (3.3.1 - 3.3.1) <D02FBB03-42A5-3E75-83C1-F563B1E3258F> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore
0x7fff8fc40000 - 0x7fff9003cfff libLAPACK.dylib (1159) <50654652-353D-3B6D-9065-8932042F3B17> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
0x7fff9003d000 - 0x7fff9003fffb libutil.dylib (43) <E37832CF-5EE6-345A-B0EC-FFC8D2B67375> /usr/lib/libutil.dylib
0x7fff90040000 - 0x7fff90042fff com.apple.loginsupport (1.0 - 1) <07F03548-C89E-3082-B170-6D03D839B551> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport
0x7fff90043000 - 0x7fff90048fff com.apple.DiskArbitration (2.7 - 2.7) <B391A885-1286-3718-A341-8C84560DDE58> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x7fff90478000 - 0x7fff9047aff7 com.apple.xpc.ServiceManagement (1.0 - 1) <0EA1807B-4F41-317D-A6C2-E6A23F201252> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
0x7fff9047b000 - 0x7fff90483fff com.apple.NetFS (6.0 - 4.0) <5602F3EB-64F6-3495-BEF0-988F92974234> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x7fff90484000 - 0x7fff90489ff7 libmacho.dylib (875.1) <A9EC23EC-11A0-3B4F-A8AC-B990C8267A6E> /usr/lib/system/libmacho.dylib
0x7fff9048a000 - 0x7fff904bbffb com.apple.GSS (4.0 - 2.0) <D50CDB44-72E9-3520-9965-93901621F781> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
0x7fff904bc000 - 0x7fff906c8ff7 com.apple.CoreImage (11.0.0 - 366) <8FEAE237-1EBA-3058-B4B3-BB36F6640F44> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
0x7fff90720000 - 0x7fff907cbfff com.apple.PDFKit (3.1 - 3.1) <165524C4-8101-341C-AD0A-CCBC1AFB0C2C> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framework/Versions/A/PDFKit
0x7fff907ce000 - 0x7fff9087efe7 libvMisc.dylib (563.3) <E594DCB8-3013-3AC1-9319-1EC47B1FCB40> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
0x7fff90951000 - 0x7fff9096cff7 libCRFSuite.dylib (34) <65E4DC91-A994-3921-B5B0-696123CE0C1E> /usr/lib/libCRFSuite.dylib
0x7fff90973000 - 0x7fff90a98ff7 com.apple.LaunchServices (728.4 - 728.4) <78774CB9-B206-360F-BC9F-2ACA69811814> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x7fff90ac7000 - 0x7fff90b0cff3 libFontRegistry.dylib (155) <BC1B3AD5-4927-3AB7-94FF-CD93BF895D98> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
0x7fff90b0d000 - 0x7fff90b1dff3 com.apple.ProtocolBuffer (1 - 242) <B3D0CEE0-1ED1-39BB-8C81-896F36398802> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer
0x7fff90b9f000 - 0x7fff90ba1fff libCGXType.A.dylib (934) <F52AC9F6-BC67-3885-9864-CDC00D9DD0AB> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib
0x7fff90c83000 - 0x7fff90cbdfff com.apple.QD (3.12 - 302) <46969760-B02A-3ED5-B8BC-D6144939B16E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
0x7fff90cbe000 - 0x7fff90daefff libJP2.dylib (1432) <FF480444-B2C9-3790-B739-0DF2B5BAD57D> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x7fff90e02000 - 0x7fff90e27ff7 libPng.dylib (1432) <975C970D-DCFA-35E4-918A-46939F279D75> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
0x7fff90e28000 - 0x7fff90e30fff libMatch.1.dylib (27) <D8024E9A-795B-30FC-BCE7-DB1E20889AB9> /usr/lib/libMatch.1.dylib
0x7fff90e31000 - 0x7fff90e39ff7 libcldcpuengine.dylib (2.6.4.1) <C33F593F-44DB-38D3-8D70-380FC401E762> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib
0x7fff90e3a000 - 0x7fff90e97fff com.apple.CoreServices.OSServices (728.4 - 728.4) <FF34E0E4-6559-3102-8833-E93DF21C9A4F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x7fff90e98000 - 0x7fff90ec1ff7 libxslt.1.dylib (14) <412A09C9-7C02-351E-A416-2453361EACA9> /usr/lib/libxslt.1.dylib
0x7fff90ec2000 - 0x7fff90ecdfff com.apple.DirectoryService.Framework (10.11 - 194) <AE493A5F-E112-39C4-AD7A-3E740A21AB42> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService
0x7fff90ece000 - 0x7fff91af0fff com.apple.AppKit (6.9 - 1404.11) <AE68D5C7-0215-3027-A54B-437B1B392CA2> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff91af7000 - 0x7fff91b01fff com.apple.NetAuth (6.0 - 6.0) <ABBBE552-26E0-3682-8BFD-C59EC702F347> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
0x7fff91b02000 - 0x7fff91b60fff com.apple.SystemConfiguration (1.14 - 1.14) <FED4C250-DDEB-3CC3-B88D-FFA56E21425E> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x7fff91b62000 - 0x7fff91bb2ff7 com.apple.Symbolication (1.4 - 58044) <BC1259C8-C671-3014-A9C4-85BC767EA962> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication
0x7fff91bb3000 - 0x7fff91bb5fff com.apple.OAuth (25 - 25) <DFC11955-75DD-303E-BFCB-0F70A4C541E0> /System/Library/PrivateFrameworks/OAuth.framework/Versions/A/OAuth
0x7fff91bb6000 - 0x7fff91be9fff com.apple.MediaKit (16 - 807) <6F40D74C-7F2C-3693-AF80-63365A6F7680> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit
0x7fff91bea000 - 0x7fff91c0bfff com.apple.Sharing (438.0.1 - 438.0.1) <10C4A9FA-47C9-37D9-A60A-C27CC57A2539> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing
0x7fff91dc7000 - 0x7fff91e77fff com.apple.backup.framework (1.7 - 1.7) <551ABBE3-211D-3D7D-B811-B2F863DD17CB> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
0x7fff91f48000 - 0x7fff9201eff7 com.apple.DiskImagesFramework (10.11 - 414) <AF08B107-F65D-36DD-9B94-A0C868C300BC> /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages
0x7fff9201f000 - 0x7fff9206aff7 com.apple.CoreMediaIO (701.0 - 4790) <999CED97-2777-37EF-8425-F25B1B1F5A04> /System/Library/Frameworks/CoreMediaIO.framework/Versions/A/CoreMediaIO
0x7fff9206b000 - 0x7fff922e8ffb com.apple.security (7.0 - 57336.1.9) <E44CA10F-E1E2-3DC5-BCF3-EF76649A0918> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff928e3000 - 0x7fff928f4fff libSparseBLAS.dylib (1159) <86AFE478-E6FB-38AB-84A3-7E4317521F2C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib
0x7fff928f5000 - 0x7fff92b61fff com.apple.imageKit (2.6 - 928) <753100AA-B8F4-3364-A111-88AAB67949B2> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit
0x7fff92b62000 - 0x7fff92b6bffb libsystem_notify.dylib (149) <56ABC155-CB99-30A8-A8B1-C204B5615092> /usr/lib/system/libsystem_notify.dylib
0x7fff92b6c000 - 0x7fff92b72ff7 com.apple.speech.recognition.framework (5.1.1 - 5.1.1) <433F8745-874A-39B3-A7C6-2EDA8C2C6B4A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
0x7fff92b88000 - 0x7fff92cacfef libsqlite3.dylib (216) <E846F7F0-F594-38B2-AA2C-210E8F4CE590> /usr/lib/libsqlite3.dylib
0x7fff92e7e000 - 0x7fff93089fff libFosl_dynamic.dylib (16.24) <7B19F360-858C-3C49-9E6D-A95CF3BE2186> /usr/lib/libFosl_dynamic.dylib
0x7fff9308a000 - 0x7fff93096fff com.apple.HelpData (2.1.4 - 90) <17295640-71FE-3D5A-887A-751D110E0630> /System/Library/PrivateFrameworks/HelpData.framework/Versions/A/HelpData
0x7fff93097000 - 0x7fff9312dff7 com.apple.ColorSync (4.9.0 - 4.9.0) <AA8AD098-1792-3803-926B-6A9DAC9CCF9A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
0x7fff9312e000 - 0x7fff93214fef unorm8_bgra.dylib (2.6.4.1) <28F838EA-19E5-3724-99FF-B61132555D09> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/ImageFormats/unorm8_bgra.dylib
0x7fff933ee000 - 0x7fff9343efff libcups.2.dylib (435) <FA565876-F9B2-3021-8E89-6D665ED01B3D> /usr/lib/libcups.2.dylib
0x7fff93447000 - 0x7fff9345efff libsystem_asl.dylib (322) <97D794DA-8CE5-3676-AC5E-364F6D172BDA> /usr/lib/system/libsystem_asl.dylib
0x7fff9345f000 - 0x7fff93473fe3 libCGInterfaces.dylib (317.2) <D7361440-5859-3804-967A-9AAA13B174FD> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib
0x7fff934bf000 - 0x7fff934f3ff7 com.apple.CoreVideo (1.8 - 191.1) <FA99D150-EFCE-3F32-ACDF-5E91AD97F176> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x7fff934fa000 - 0x7fff93514ff3 liblzma.5.dylib (10) <8CD18286-49EA-31E4-8A73-1BF8DECED6C6> /usr/lib/liblzma.5.dylib
0x7fff935d8000 - 0x7fff9367ffff com.apple.LanguageModeling (1.0 - 1) <C405E993-F0DF-39E4-9B74-FE310E63DD8E> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling
0x7fff93680000 - 0x7fff936f6ff7 com.apple.MMCS (1.3 - 349) <C445C851-09F2-34F8-AA4C-D7135C15945F> /System/Library/PrivateFrameworks/MMCS.framework/Versions/A/MMCS
0x7fff936fa000 - 0x7fff936fbfff libDiagnosticMessagesClient.dylib (100) <F2D8CFCC-A00A-3675-9C01-EF0C663F2445> /usr/lib/libDiagnosticMessagesClient.dylib
0x7fff93766000 - 0x7fff93798fff libTrueTypeScaler.dylib (158) <A885D75F-5B7D-3BC8-9D2B-FB6D2D831368> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib
0x7fff937db000 - 0x7fff93907ff7 com.apple.CoreText (352.0 - 494.3) <2A5DCA97-300D-36FB-9E94-3041CFF6D615> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
0x7fff93908000 - 0x7fff9390aff7 libsystem_configuration.dylib (801.1.1) <EB55C3D8-048D-350E-BF24-0CBD4479D51C> /usr/lib/system/libsystem_configuration.dylib
0x7fff9390b000 - 0x7fff9397fff3 com.apple.securityfoundation (6.0 - 55126) <C2DFA113-1814-3701-B185-D82E11A26E86> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
0x7fff9398f000 - 0x7fff93c74ff3 com.apple.CoreServices.CarbonCore (1136 - 1136) <9DE930A3-63C0-3E21-965A-132D97D61892> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x7fff93c75000 - 0x7fff93cadfff com.apple.RemoteViewServices (2.0 - 99) <8BD12AE2-BE91-37CF-955B-62E08551FF83> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices
0x7fff93cae000 - 0x7fff94204ff7 com.apple.MediaToolbox (1.0 - 1731.15.4) <BA54842F-7017-3E07-98A5-94E59C462929> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox
0x7fff94221000 - 0x7fff94575ff7 com.apple.Foundation (6.9 - 1252) <2D13ED37-BFFE-3B7F-A65A-D6ED43B05EE9> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff94576000 - 0x7fff945d4fff libsystem_network.dylib (582.1.4) <14ECA259-D471-3E47-A843-FF0990577893> /usr/lib/system/libsystem_network.dylib
0x7fff945da000 - 0x7fff94651fc7 libcorecrypto.dylib (334) <4E1B969F-8449-3B21-9880-51AD58E25AA6> /usr/lib/system/libcorecrypto.dylib
0x7fff94652000 - 0x7fff948d9ff3 com.apple.CFNetwork (760.0.5 - 760.0.5) <66C3378C-430D-3803-8025-66120AFDCD16> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x7fff94a1f000 - 0x7fff94a2afff com.apple.CommerceCore (1.0 - 453) <2E605FE7-DEB6-354E-A6E1-E9D24D8E7B69> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCore.framework/Versions/A/CommerceCore
0x7fff94a2b000 - 0x7fff94a2bff7 liblaunch.dylib (755.1.19) <7EC0F297-43CC-3D11-B46B-7E72E372648A> /usr/lib/system/liblaunch.dylib
0x7fff94a44000 - 0x7fff94a8aff7 libauto.dylib (186) <460B0167-C89B-37EC-823C-52F684B31C26> /usr/lib/libauto.dylib
0x7fff94a8b000 - 0x7fff94a93fff libGFXShared.dylib (12.0.34.11) <011CCF06-3F8D-3695-A60F-E67F72FF1583> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
0x7fff94ad2000 - 0x7fff94bb2ff7 unorm8_rgba.dylib (2.6.4.1) <49FF2837-D97B-3CFF-B139-E57D40700F32> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/ImageFormats/unorm8_rgba.dylib
0x7fff94bb3000 - 0x7fff94c05fff com.apple.ImageCaptureCore (7.0 - 7.0) <74BC5DBA-FD63-31B9-A55B-C3C128852F1D> /System/Library/Frameworks/ImageCaptureCore.framework/Versions/A/ImageCaptureCore
0x7fff94c11000 - 0x7fff94c5ffff libcurl.4.dylib (90) <00662A4C-B89A-3A17-93FF-950C6DE47F99> /usr/lib/libcurl.4.dylib
0x7fff94c7a000 - 0x7fff94c8bfff libz.1.dylib (60) <43317BEA-ACA2-34C2-AF37-902AA926C83A> /usr/lib/libz.1.dylib
0x7fff94c8c000 - 0x7fff94cfffff com.apple.framework.IOKit (2.0.2 - 1178.1.4) <B30239A0-B11E-36E9-AB49-2C53942A6447> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff94d97000 - 0x7fff94d9cfff com.apple.TCC (1.0 - 1) <8D7468B6-D5A3-3BF9-BD98-E8087AF0B61B> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
0x7fff94df9000 - 0x7fff94dfbfff libsystem_coreservices.dylib (19) <692631A0-1923-32CA-9BD5-044B1382FFDE> /usr/lib/system/libsystem_coreservices.dylib
0x7fff94dfc000 - 0x7fff94e12ff7 libLinearAlgebra.dylib (1159) <01BD9187-521F-3F96-B477-24511318AECD> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
0x7fff94e13000 - 0x7fff94e15ff7 libquarantine.dylib (80) <1693C5FE-EA0A-3122-85EB-7950ECC7435A> /usr/lib/system/libquarantine.dylib
0x7fff94e2c000 - 0x7fff94eccfff com.apple.ViewBridge (157 - 157) <78610813-8150-3DD5-823D-F0ECDB0A583F> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge
0x7fff94f8a000 - 0x7fff94fb1ff7 com.apple.ProtectedCloudStorage (1.0 - 1) <EA83603A-7C4D-37F1-A416-064CD1B9D34B> /System/Library/PrivateFrameworks/ProtectedCloudStorage.framework/Versions/A/ProtectedCloudStorage
0x7fff94fb2000 - 0x7fff94fbafff com.apple.frameworks.CoreDaemon (1.3 - 1.3) <B0028247-B333-36F5-8098-8EC95E6C2B23> /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon
0x7fff95001000 - 0x7fff950f3ff7 libiconv.2.dylib (44) <82529E3B-0485-344C-8075-83C7725D6A6F> /usr/lib/libiconv.2.dylib
0x7fff9521b000 - 0x7fff955b0fdf com.apple.vImage (8.0 - 8.0) <3DEF81C9-CD75-32BF-A927-4FCD89D57190> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x7fff95786000 - 0x7fff957afff7 libsystem_info.dylib (476) <65D0643A-C8AE-3E8D-9F6E-E4AD823F16B2> /usr/lib/system/libsystem_info.dylib
0x7fff957b0000 - 0x7fff95b88fef com.apple.CoreAUC (214.0.0 - 214.0.0) <36675355-FEF4-3DC0-9734-AE6F125883C2> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC
0x7fff95b8b000 - 0x7fff95bc9ff7 libGLImage.dylib (12.0.34.11) <057F9F59-B58A-3C8D-A965-F4929A212406> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x7fff95bca000 - 0x7fff95bcefff libcache.dylib (75) <4948E2C8-867F-3E9D-AAE7-2F30F0B345C6> /usr/lib/system/libcache.dylib
0x7fff95c07000 - 0x7fff95c94fff com.apple.CorePDF (4.0 - 4) <EDC193AE-0D72-3BDD-807D-28D1A5942AE3> /System/Library/PrivateFrameworks/CorePDF.framework/Versions/A/CorePDF
0x7fff95cf4000 - 0x7fff95d2eff7 com.apple.DebugSymbols (132 - 132) <6F5853A1-5DA8-3C42-8E02-2B972F34BCE0> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols
0x7fff95d37000 - 0x7fff95fcaff7 libmecabra.dylib (696) <55386F90-7260-38EC-BA41-897865944908> /usr/lib/libmecabra.dylib
0x7fff95fcb000 - 0x7fff95fd6fff com.apple.AppSandbox (4.0 - 261.1.1) <39C1D57B-457A-39BD-BB0A-9B8C5D8C986E> /System/Library/PrivateFrameworks/AppSandbox.framework/Versions/A/AppSandbox
0x7fff95fe9000 - 0x7fff95febff7 com.apple.SecCodeWrapper (4.0 - 261.1.1) <2CAEF317-4FB1-3A88-BF83-975469C7F272> /System/Library/PrivateFrameworks/SecCodeWrapper.framework/Versions/A/SecCodeWrapper
0x7fff96003000 - 0x7fff9600bfff libcopyfile.dylib (127) <CA2602AB-E8B7-3CD8-A0C5-D86E35FDA09F> /usr/lib/system/libcopyfile.dylib
0x7fff9600c000 - 0x7fff9601afff libxar.1.dylib (302) <898402AF-0DF3-341D-83EA-4A1B1770E718> /usr/lib/libxar.1.dylib
0x7fff9603e000 - 0x7fff96080ff7 com.apple.Metal (54.26.3 - 54.26.3) <9000AE52-6638-309E-90A5-CB18C83A0A0E> /System/Library/Frameworks/Metal.framework/Versions/A/Metal
0x7fff962d8000 - 0x7fff962d8fff com.apple.Carbon (154 - 157) <DF95E7EB-1CFC-3C83-B114-60FFEEAE166E> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x7fff965be000 - 0x7fff96678fff com.apple.DiscRecording (9.0.1 - 9010.4.3) <9E68D2AF-7205-3764-B051-8F112AFA8208> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
0x7fff96680000 - 0x7fff9688dfff libicucore.A.dylib (551.24) <DEB70F32-DA94-323B-B6D1-03D09C8FB10C> /usr/lib/libicucore.A.dylib
0x7fff968f2000 - 0x7fff96961fff com.apple.SearchKit (1.4.0 - 1.4.0) <45A716CD-D9E7-3F1F-9EC8-BB37CA9E8C04> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x7fff96962000 - 0x7fff969a7ff7 com.apple.coreservices.SharedFileList (24.2 - 24.2) <07212306-2DBC-303B-B042-4C02E70F073C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList
0x7fff969b4000 - 0x7fff969b4fff com.apple.CoreServices (728.4 - 728.4) <208E32DA-E7D9-3B4F-A545-EE2BFB53696D> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fff974bc000 - 0x7fff98702fe3 com.apple.CoreGraphics (1.600.0 - 934) <D2175CEA-C733-34C4-A0F0-3F6C36897333> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x7fff98703000 - 0x7fff9870cff7 com.apple.DisplayServicesFW (3.0 - 378) <69821BC1-66F6-30FE-B706-134F3A9FCAD7> /System/Library/PrivateFrameworks/DisplayServices.framework/Versions/A/DisplayServices
0x7fff9870d000 - 0x7fff9877efff com.apple.ApplicationServices.ATS (377 - 394) <BCFC24A8-6ACA-3B90-8896-019F38A649F6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
0x7fff9877f000 - 0x7fff9879cfff com.apple.AppleVPAFramework (2.0.15 - 2.0.15) <2847B765-B0A9-3D74-BDEF-556795270AE1> /System/Library/PrivateFrameworks/AppleVPA.framework/Versions/A/AppleVPA
0x7fff9879d000 - 0x7fff987bcff7 com.apple.framework.Apple80211 (11.0 - 1101.30) <7A0350BD-18E0-38F3-80F2-EABD1643BA2D> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
0x7fff987bd000 - 0x7fff987c1fff libpam.2.dylib (20) <7F986CE8-EF74-3BC3-BB7E-5267E24EAFFE> /usr/lib/libpam.2.dylib
0x7fff987f3000 - 0x7fff98853ff7 com.apple.QuickLookFramework (5.0 - 696.1) <727FE6BE-8E92-38A3-BDEB-2410B553BB27> /System/Library/Frameworks/QuickLook.framework/Versions/A/QuickLook
0x7fff98854000 - 0x7fff98870ff7 libsystem_malloc.dylib (67) <1B57A614-3D60-3F87-876F-7DB4AF38120F> /usr/lib/system/libsystem_malloc.dylib
0x7fff98871000 - 0x7fff9887ffff com.apple.ToneLibrary (1.0 - 1) <E8B44453-4E70-393C-AECF-988D0A8284A6> /System/Library/PrivateFrameworks/ToneLibrary.framework/Versions/A/ToneLibrary
0x7fff98880000 - 0x7fff98885fff com.apple.AssetCacheServices (14 - 14) <8C912A44-6635-33A0-82A3-389585BAC0F1> /System/Library/PrivateFrameworks/AssetCacheServices.framework/Versions/A/AssetCacheServices
0x7fff98886000 - 0x7fff98887fff libsystem_blocks.dylib (65) <1B4F1F10-823E-3781-8162-6884D14DF0D6> /usr/lib/system/libsystem_blocks.dylib
0x7fff98888000 - 0x7fff988aaff7 com.apple.IconServices (68 - 68) <9F8B9184-8DA8-3B7A-970B-3086DDD1CC6F> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices
0x7fff988ab000 - 0x7fff98907fef libTIFF.dylib (1432) <0E036A7E-5581-3727-95C6-A3359C76BC5C> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x7fff98caf000 - 0x7fff98cc4fff com.apple.ToneKit (1.0 - 1) <3722D681-0582-335A-A992-A972D2046163> /System/Library/PrivateFrameworks/ToneKit.framework/Versions/A/ToneKit
0x7fff98cc5000 - 0x7fff98cd0fff libkxld.dylib (3247.1.106) <D38002C3-A391-361B-ACD3-5FF2EDA51EDC> /usr/lib/system/libkxld.dylib
0x7fff993bf000 - 0x7fff993bffff com.apple.Cocoa (6.11 - 22) <A033F342-1FEC-3DFD-830A-E8EE284DF492> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x7fff993c0000 - 0x7fff993c3fff libspindump.dylib (197) <D55A6D6B-7B7D-3D15-AC6C-73DE9954C671> /usr/lib/libspindump.dylib
0x7fff993c4000 - 0x7fff993c5fff liblangid.dylib (122) <EAC09BF0-5E88-3060-AA51-EC71B4D26F3C> /usr/lib/liblangid.dylib
0x7fff993c6000 - 0x7fff993c9fff libsystem_sandbox.dylib (459.1.8) <2F36D536-482C-39EC-BAFD-72297728F0A4> /usr/lib/system/libsystem_sandbox.dylib
0x7fff993ca000 - 0x7fff99419ff7 com.apple.opencl (2.6.9 - 2.6.9) <68A63931-3F6F-3DE2-9C8D-624006908B83> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
0x7fff99d9d000 - 0x7fff99d9dfff libenergytrace.dylib (10) <64F779D4-2192-37EC-8DB5-EC55BAE50058> /usr/lib/libenergytrace.dylib
0x7fff99dae000 - 0x7fff99db1fff com.apple.IOSurface (108.0.1 - 108.0.1) <43D70E5A-64F5-384A-A95E-64253538C24F> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
0x7fff9a08e000 - 0x7fff9a090ff7 com.apple.securityhi (9.0 - 55006) <A46A58CB-E0AA-3EBD-AABF-A3B219A18ACF> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
0x7fff9a09d000 - 0x7fff9a132fff com.apple.ink.framework (10.9 - 214) <F1B3B6C9-FF8D-3E68-93EB-8CDCEB65171A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
0x7fff9a133000 - 0x7fff9a222fff libxml2.2.dylib (29) <0702E13C-D726-3DAF-B0D1-77F7B9EF6A37> /usr/lib/libxml2.2.dylib
0x7fff9a2d6000 - 0x7fff9a3e4fff com.apple.desktopservices (1.10 - 1.10) <76AA21FE-0F96-366A-9B43-6188FBC29ABE> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
0x7fff9a3e5000 - 0x7fff9a410ff3 libarchive.2.dylib (32) <731529D2-1178-3742-AFE0-6CA8568FBB19> /usr/lib/libarchive.2.dylib
0x7fff9a411000 - 0x7fff9a440fff com.apple.securityinterface (10.0 - 55065) <8F140606-7DDA-34D0-823E-514994E0DE8A> /System/Library/Frameworks/SecurityInterface.framework/Versions/A/SecurityInterface
0x7fff9a441000 - 0x7fff9a4caff7 com.apple.PerformanceAnalysis (1.0 - 1) <E7C53B84-558F-39EA-949C-82F4163F6F14> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis
0x7fff9a4cb000 - 0x7fff9a4d0ff7 libheimdal-asn1.dylib (452.1.1) <6E911973-1E1A-3F80-B955-FA78CF20FBFD> /usr/lib/libheimdal-asn1.dylib
0x7fff9a4d1000 - 0x7fff9a4e0ffb com.apple.LangAnalysis (1.7.0 - 1.7.0) <E7D610A1-1445-3CA3-B9A1-EE15D54B75AB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
0x7fff9a543000 - 0x7fff9a5d0dd7 com.apple.AppleJPEG (1.0 - 1) <6230F3A0-C89D-3A35-A896-A17B3513E8DB> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
0x7fff9a5d1000 - 0x7fff9a61dffb com.apple.HIServices (1.22 - 548) <19389B63-C373-31AE-9180-3A11093EAE58> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
0x7fff9a688000 - 0x7fff9a783fff libFontParser.dylib (158) <3CD078A8-2E20-3B0F-B312-A2E641C76873> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
0x7fff9a7bb000 - 0x7fff9a893fff com.apple.CoreMedia (1.0 - 1731.15.4) <30C4C79B-38E7-331F-A3D1-8D0777D23FD4> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
0x7fff9a894000 - 0x7fff9a89dff7 libsystem_pthread.dylib (137.1.1) <1373D0F1-C6CA-364E-A6BA-8BDBD0D34670> /usr/lib/system/libsystem_pthread.dylib
0x7fff9a8e1000 - 0x7fff9a8fdff3 libresolv.9.dylib (60) <B192EC27-84EC-3D8A-9CBF-0374B5C9B31A> /usr/lib/libresolv.9.dylib
0x7fff9a91a000 - 0x7fff9ab65fff com.apple.AddressBook.framework (9.0 - 1679) <26FE27B6-40B7-3633-906D-5323ACEE3337> /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
0x7fff9ab66000 - 0x7fff9ab96ff7 libsandbox.1.dylib (459.1.8) <46104D7B-2B76-3C3C-A551-9DED100A2D8B> /usr/lib/libsandbox.1.dylib
0x7fff9ab97000 - 0x7fff9ab99fff com.apple.CoreDuetDebugLogging (1.0 - 1) <B390CD9A-A04F-3A9E-A40C-CB317F40AFE5> /System/Library/PrivateFrameworks/CoreDuetDebugLogging.framework/Versions/A/CoreDuetDebugLogging
0x7fff9ac30000 - 0x7fff9ac82fff com.apple.CloudDocs (1.0 - 382) <F8B381F5-C434-3719-B26B-137D61F8DEBD> /System/Library/PrivateFrameworks/CloudDocs.framework/Versions/A/CloudDocs
0x7fff9ac8c000 - 0x7fff9ac94ffb libsystem_dnssd.dylib (624.1.2) <DB6AB206-4AD8-369D-BF57-1D246AD60582> /usr/lib/system/libsystem_dnssd.dylib
0x7fff9ac95000 - 0x7fff9ae3cffb com.apple.avfoundation (2.0 - 1046.9.1) <BFA3AB94-F05C-3827-BD20-4BE3DC6F3AAC> /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation
0x7fff9afc2000 - 0x7fff9afddfff com.apple.aps.framework (4.0 - 4.0) <A3971E50-DD87-3752-B37A-E58557AD5AF2> /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService
0x7fff9afde000 - 0x7fff9b1a4fef com.apple.ImageIO.framework (3.3.0 - 1432) <06EADBB8-54E0-39B5-BAA4-935FE9E62FE4> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x7fff9b1ab000 - 0x7fff9b1b7fff com.apple.SpeechRecognitionCore (2.2.7 - 2.2.7) <12117823-8A9E-3C88-A01C-3B25D68535CE> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore
0x7fff9b1b8000 - 0x7fff9b1bbfff libCoreVMClient.dylib (119.5) <3B709F2E-35BA-3D96-9324-E56AF5F68E50> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
0x7fff9b1cf000 - 0x7fff9b1d5fff com.apple.XPCService (2.0 - 1) <E50F1206-8B6B-3CDB-BC66-E5B70B4B41C7> /System/Library/PrivateFrameworks/XPCService.framework/Versions/A/XPCService
0x7fff9b1d6000 - 0x7fff9b1e1fff com.apple.CrashReporterSupport (10.11 - 715) <D0D22E00-4DA0-3AEF-8522-0814F9070666> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport
0x7fff9b22a000 - 0x7fff9b235ff7 libcommonCrypto.dylib (60074) <BD1DCF19-8353-3F6A-AFFA-EBBA29A302A8> /usr/lib/system/libcommonCrypto.dylib
0x7fff9b237000 - 0x7fff9b24bfff libsystem_coretls.dylib (82) <21EDACF1-D9B3-3086-9821-60EB75E7F965> /usr/lib/system/libsystem_coretls.dylib
0x7fff9b27c000 - 0x7fff9b27eff7 libRadiance.dylib (1432) <576E5580-A695-320E-9525-103FCD723137> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x7fff9c4ef000 - 0x7fff9c562ffb com.apple.Heimdal (4.0 - 2.0) <2D358FB4-61BB-3BB6-9EF7-D9868A0B0275> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
0x7fff9c64b000 - 0x7fff9c657ff7 com.apple.OpenDirectory (10.11 - 194) <E0F63D60-23C8-3FB7-BA78-5BD861354352> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
0x7fff9c8c2000 - 0x7fff9c8c2ff7 libunc.dylib (29) <D9B0C7B1-8648-3AAC-931C-E7CD362FAA8A> /usr/lib/system/libunc.dylib
0x7fff9c8c3000 - 0x7fff9c918fff com.apple.AE (701 - 701) <87FDCC5A-82AC-36A2-BFE9-D0B2A3D870F1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x7fff9c919000 - 0x7fff9c92ffff com.apple.CoreMediaAuthoring (2.2 - 953) <82B62463-6125-3B03-AA57-8724E13C7F41> /System/Library/PrivateFrameworks/CoreMediaAuthoring.framework/Versions/A/CoreMediaAuthoring
0x7fff9cb35000 - 0x7fff9cb37fff libCVMSPluginSupport.dylib (12.0.34.11) <36238490-6F35-35CA-B0B8-4032ABA7C537> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
0x7fff9cb38000 - 0x7fff9cb3bffb libdyld.dylib (360.14) <F9D64D8C-4C33-3D06-B7F8-697F13292894> /usr/lib/system/libdyld.dylib
0x7fff9cb3c000 - 0x7fff9ccbafff com.apple.UIFoundation (1.0 - 435) <237F281F-7F15-3309-B749-F8DA37822F9F> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation
0x7fff9ccf7000 - 0x7fff9ccfcfff com.apple.ImageCapture (9.0 - 9.0) <E53CC0B8-9D36-3636-B602-8AB4CEB4C313> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
0x7fff9ccfd000 - 0x7fff9cd2bff7 com.apple.CoreServicesInternal (248 - 248) <EAD7A7B3-D775-3E4C-98B8-36D047795993> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal
0x7fff9cdb7000 - 0x7fff9d224ffb com.apple.GeoServices (1.0 - 1151.2.13.1) <13CD8BAC-6DFD-3BD1-A2C4-683D5E2DE330> /System/Library/PrivateFrameworks/GeoServices.framework/Versions/A/GeoServices
0x7fff9d225000 - 0x7fff9d270ffb com.apple.print.framework.PrintCore (11.0 - 472) <34EA102A-D482-37FF-9C9B-E4FE4275913B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
0x7fff9d4b6000 - 0x7fff9d556fff com.apple.Metadata (10.7.0 - 972.9) <83FB4CDD-29DE-3DAD-8FEB-FD9E9474576F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x7fff9d557000 - 0x7fff9d558ffb libSystem.B.dylib (1225.1.1) <E48AAE3F-370E-34AE-AECA-4CA28F211479> /usr/lib/libSystem.B.dylib
0x7fff9d55c000 - 0x7fff9d56efff com.apple.contacts.ContactsPersistence (1.0 - 2137) <40E67B07-5DC9-3B5E-8266-1A27142268D0> /System/Library/PrivateFrameworks/ContactsPersistence.framework/Versions/A/ContactsPersistence
0x7fff9d576000 - 0x7fff9da98fff com.apple.QuartzComposer (5.1 - 334) <B28D6929-25C0-3F27-9454-EAE22857EF4A> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzComposer.framework/Versions/A/QuartzComposer
0x7fff9dbf2000 - 0x7fff9dbf6fff com.apple.CommonPanels (1.2.6 - 96) <1D76DDD3-D45A-3679-8B72-5EECE6C1ACAC> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
0x7fff9dbf7000 - 0x7fff9dc48ff7 com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <E9B6EFBA-F6EA-3F20-8C91-53EC7D464773> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x7fff9dc70000 - 0x7fff9dcfcfff libCoreStorage.dylib (517) <753BB578-62C6-36F8-B366-72EF7742D42B> /usr/lib/libCoreStorage.dylib
0x7fff9dd93000 - 0x7fff9dd95ff7 com.apple.ExceptionHandling (1.5 - 11) <A7C5ADB2-08FF-3B27-95C7-1F0F3E842C59> /System/Library/Frameworks/ExceptionHandling.framework/Versions/A/ExceptionHandling
0x7fff9dd9b000 - 0x7fff9dd9eff7 libCoreFSCache.dylib (119.5) <9BFF447F-D571-3EE6-860E-29886F1F913F> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
0x7fff9dd9f000 - 0x7fff9dd9ffff libmetal_timestamp.dylib (600.0.41.2) <C8548755-D695-380D-991E-A94484084B6E> /System/Library/PrivateFrameworks/GPUCompiler.framework/libmetal_timestamp.dylib
0x7fff9dda0000 - 0x7fff9de0fffb com.apple.datadetectorscore (7.0 - 460) <65672990-505F-3B1D-87FB-42BE532A4D07> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
0x7fff9de10000 - 0x7fff9de21fff libcmph.dylib (6) <43880250-9C2D-395C-90C7-CCCE109FF1B2> /usr/lib/libcmph.dylib
0x7fff9de22000 - 0x7fff9de32fff libbsm.0.dylib (34) <F1E41935-5C5D-3704-AE9D-AEA1F2BCF8B1> /usr/lib/libbsm.0.dylib
0x7fff9de33000 - 0x7fff9e4d8ff3 com.apple.JavaScriptCore (11601 - 11601.1.56) <1FC92922-FBCD-3EA4-AE13-F2F05525A125> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
0x7fff9e6c0000 - 0x7fff9e70cff7 com.apple.corelocation (1486.17 - 1615.36) <57417982-D0E1-3835-B705-A0242E65C5E4> /System/Library/Frameworks/CoreLocation.framework/Versions/A/CoreLocation
0x7fff9e73b000 - 0x7fff9e768fff libdispatch.dylib (500.1.5) <6B38497E-9448-3433-9D6B-6223F2A99431> /usr/lib/system/libdispatch.dylib
0x7fff9e769000 - 0x7fff9e76dfff libGIF.dylib (1432) <4C5B63B4-ABCA-3A99-A69F-D0E27E87E5A3> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x7fff9e76e000 - 0x7fff9e773ff3 libunwind.dylib (35.3) <FDA18078-A775-3BAF-A5A6-8A7B75D6AA99> /usr/lib/system/libunwind.dylib
0x7fff9e77b000 - 0x7fff9e77bfff com.apple.Accelerate (1.10 - Accelerate 1.10) <524AF1B0-1E45-3F03-83FF-493F9F8E1FF8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x7fff9e77e000 - 0x7fff9e7ccff7 libstdc++.6.dylib (104.1) <77780A99-22DB-35AA-BD9E-ADB83417E4BD> /usr/lib/libstdc++.6.dylib
0x7fff9e7cd000 - 0x7fff9e7d5fff com.apple.CoreServices.FSEvents (1222.1.1 - 1222.1.1) <79DF16A7-E169-38A5-BF5E-2D45F86DE154> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents
0x7fff9e7d6000 - 0x7fff9e7ebfff com.apple.AppContainer (4.0 - 261.1.1) <6F31BB33-0D51-3A4D-A7DD-42446BF43DA0> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer
0x7fff9e869000 - 0x7fff9ea0eff3 com.apple.audio.toolbox.AudioToolbox (1.13 - 1.13) <7380C7DA-7CE8-34DF-BB3D-DAFE9406674F> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x7fff9ea0f000 - 0x7fff9ea21fff libsasl2.2.dylib (209) <D48CE2C5-D0C5-39BD-A7DD-C999E81CF885> /usr/lib/libsasl2.2.dylib
0x7fff9ea59000 - 0x7fff9ea64fff libGL.dylib (12.0.34.11) <C7196A5D-3BC1-301A-9695-A9122BC773B3> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x7fff9ea65000 - 0x7fff9ed0bfff com.apple.CoreData (120 - 640) <7934FDB8-526E-32F4-BE20-55388DB8CCBF> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x7fff9ed11000 - 0x7fff9ed17fff com.apple.IOAccelerator (203.7.1 - 203.7.1) <68212F3D-7660-3391-89CA-99363ED9AB4D> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator
0x7fff9ed18000 - 0x7fff9ed18fff com.apple.quartzframework (1.5 - 21) <E37B0DA2-8DEB-3D46-9038-BD91E789A375> /System/Library/Frameworks/Quartz.framework/Versions/A/Quartz
0x7fff9ed19000 - 0x7fff9ed24ff7 libChineseTokenizer.dylib (16) <1794A880-9C3D-37B2-8F3E-6CAFFB396089> /usr/lib/libChineseTokenizer.dylib
0x7fff9edd6000 - 0x7fff9edd6ff7 libkeymgr.dylib (28) <47080280-8B57-3D75-8A20-9E100864DE27> /usr/lib/system/libkeymgr.dylib
0x7fff9eddc000 - 0x7fff9edfafff libsystem_kernel.dylib (3247.1.106) <7DD242A1-E2BF-39D1-8787-B174046E4F15> /usr/lib/system/libsystem_kernel.dylib
0x7fff9ee00000 - 0x7fff9ee08fef libsystem_platform.dylib (73.1.1) <3F4D2390-E3DE-3C24-A515-95DFAC8671C4> /usr/lib/system/libsystem_platform.dylib
0x7fff9ee09000 - 0x7fff9efd7ff7 com.apple.QuartzCore (1.11 - 410.7) <3DDB2E3A-6902-3216-8DC4-56ED16B7C698> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x7fff9f1fd000 - 0x7fff9f1fdfff com.apple.audio.units.AudioUnit (1.13 - 1.13) <017C6053-C32E-34EE-AAAE-6702E74F14EF> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x7fff9f27d000 - 0x7fff9f305fff com.apple.CoreSymbolication (3.1 - 58048.1) <CC7CAE84-DEC6-3184-B841-559DBE97D025> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication
0x7fff9f4ae000 - 0x7fff9f4b3fff com.apple.MediaAccessibility (1.0 - 79) <309526B0-1A18-3C2D-B425-A2BB61EED005> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility
0x7fff9f4b4000 - 0x7fff9f4ccfcf libcompression.dylib (23) <7467B2EB-E0E0-3E9D-9EAD-3E04500C6395> /usr/lib/libcompression.dylib
0x7fff9f4cd000 - 0x7fff9f4e7fff com.apple.Kerberos (3.0 - 1) <D2F0BF94-8656-3FBF-81AC-43D417B661F1> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x7fff9f4ee000 - 0x7fff9f869ffb com.apple.VideoToolbox (1.0 - 1731.15.4) <72715A24-C3BC-35D8-8240-BBBD56E37090> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox
0x7fff9f87e000 - 0x7fff9f8e8ff7 com.apple.framework.CoreWLAN (11.0 - 1100.19) <3CA2F32A-4FBF-39ED-83EC-F2E3C43D3775> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
0x7fff9f8ed000 - 0x7fff9f8edfff com.apple.ApplicationServices (48 - 48) <B5326BD2-AF17-3880-A8C5-3C990AE4A1C8> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x7fff9f8ee000 - 0x7fff9f926ff7 com.apple.Accounts (113 - 113) <689EE961-FC8D-3225-AD29-8AECDDB5AEBE> /System/Library/Frameworks/Accounts.framework/Versions/A/Accounts
0x7fff9f936000 - 0x7fff9f95fffb libRIP.A.dylib (934) <DB727879-E42B-33C5-B1FF-CC34CDFBF017> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x7fff9f9b1000 - 0x7fff9f9b2fff com.apple.TrustEvaluationAgent (2.0 - 25) <BC19A1D1-805B-3FC5-BF0B-1EF6FB36FE74> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent
0x7fff9fae6000 - 0x7fff9fb27ff7 libGLU.dylib (12.0.34.11) <4F500E40-33FD-3EFF-8513-E553E3B4D560> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 3
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 292889
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=328.2M resident=0K(0%) swapped_out_or_unallocated=328.2M(100%)
Writable regions: Total=566.5M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=566.5M(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Accelerate.framework 128K 2
Activity Tracing 2048K 2
CG backing stores 17.8M 4
CG image 36K 5
CG shared images 272K 8
CoreAnimation 20K 5
CoreUI image data 668K 19
CoreUI image file 192K 4
Dispatch continuations 16.0M 2
Foundation 36K 2
Kernel Alloc Once 8K 3
MALLOC 38.4M 16
MALLOC guard page 32K 7
Memory Tag 242 12K 2
OpenCL 8K 2
Process Corpse Info 2048K 2
STACK GUARD 56.3M 69
Stack 45.5M 69
VM_ALLOCATE 427.4M 355
__DATA 31.2M 283
__IMAGE 528K 2
__LINKEDIT 88.7M 14
__TEXT 239.5M 291
__UNICODE 552K 2
mapped file 1.6G 176
shared memory 16.3M 8
=========== ======= =======
TOTAL 2.6G 1328
Model: MacBookPro11,3, BootROM MBP112.0138.B15, 4 processors, Intel Core i7, 2.3 GHz, 16 GB, SMC 2.19f12
Graphics: Intel Iris Pro, Intel Iris Pro, Built-In
Graphics: NVIDIA GeForce GT 750M, NVIDIA GeForce GT 750M, PCIe, 2048 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (7.21.94.25.1a3)
Bluetooth: Version 4.4.0f4 16320, 3 services, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0512F, 500.28 GB
USB Device: USB 3.0 Bus
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1
**Trac**:
**Username**: sordidhttps://gitlab.torproject.org/legacy/trac/-/issues/17401use-after-free in validate_intro_point_failure2020-06-13T14:50:36ZNick Mathewsonuse-after-free in validate_intro_point_failureIn validate_intro_point_failure(), we look at `identity` after freeing `intro`. But `identity` is a reference into `intro`, so we shouldn't free `intro` till we're done with it.In validate_intro_point_failure(), we look at `identity` after freeing `intro`. But `identity` is a reference into `intro`, so we shouldn't free `intro` till we're done with it.Tor: 0.2.7.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/17402Memory leak in rend_cache_failure_entry_free()2020-06-13T14:50:36ZNick MathewsonMemory leak in rend_cache_failure_entry_free()Tor: 0.2.7.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/17404dn_indicates_v3_cert can call memcmp up to 4 chars before the beginning of a ...2020-06-13T14:50:37ZNick Mathewsondn_indicates_v3_cert can call memcmp up to 4 chars before the beginning of a string.dn_indicates_v3_cert() does this:
```
len = ASN1_STRING_to_UTF8(&s, str);
if (len < 0) {
return 0;
}
r = fast_memneq(s + len - 4, ".net", 4);
```
Note that if the len < 4, we read bytes from a malloc header, which isn't a go...dn_indicates_v3_cert() does this:
```
len = ASN1_STRING_to_UTF8(&s, str);
if (len < 0) {
return 0;
}
r = fast_memneq(s + len - 4, ".net", 4);
```
Note that if the len < 4, we read bytes from a malloc header, which isn't a good thing at all.
In practice, I don't think this should cause crashes or security failures, unless somebody is using a very weird malloc, or unless somebody has a hardened installation that detects this kind of invalid check.
Still, this is a must-fix.Tor: 0.2.4.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/17474tor messenger2018-10-21T23:20:07ZTractor messengerhave install tor messenger and dont come upp wen have click on it???
**Trac**:
**Username**: hawkenhave install tor messenger and dont come upp wen have click on it???
**Trac**:
**Username**: hawkenhttps://gitlab.torproject.org/legacy/trac/-/issues/17484Tor Messenger font size settings2016-11-05T19:25:13ZColin ChildsTor Messenger font size settingsWhen you go into the Tor Messenger preferences and adjust font size, it does not seem to actually perform the font size adjustment in the application.When you go into the Tor Messenger preferences and adjust font size, it does not seem to actually perform the font size adjustment in the application.Sukhbir SinghSukhbir Singhhttps://gitlab.torproject.org/legacy/trac/-/issues/17491Orbot crashes when App-mode is enabled2020-06-13T04:41:31ZTracOrbot crashes when App-mode is enabledWhen I enable App-mode after Orbot is connected, Orbot will crash when I open a network connection.
When I look into the processes in Settings - Apps, Orbot is still running with 1 process and 1 service but the app itself shows that it i...When I enable App-mode after Orbot is connected, Orbot will crash when I open a network connection.
When I look into the processes in Settings - Apps, Orbot is still running with 1 process and 1 service but the app itself shows that it is not connected anymore and is not able to connect anymore
"Failed to parse validate config: Failed to bind one of the listener ports."
I see this behavior on a Moto X 2013 with CyanogenMod 12.1 and on a LG G4 with Android 5.1
**Trac**:
**Username**: nielskNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/17550All UI elements appear really messed up (Windows 10 JA)2020-06-15T23:31:19ZYawning AngelAll UI elements appear really messed up (Windows 10 JA)This happens on Windows 10(JA) with either the 5.5a4_en-US bundle or the 5.5a4_ja bundle.
All the UI elements including the initial configuration dialog box are appear to be sized incorrectly.This happens on Windows 10(JA) with either the 5.5a4_en-US bundle or the 5.5a4_ja bundle.
All the UI elements including the initial configuration dialog box are appear to be sized incorrectly.https://gitlab.torproject.org/legacy/trac/-/issues/17558Sanitize copying to clipboard2020-06-15T23:31:20ZcypherpunksSanitize copying to clipboardLet's consider a simple scenario
1 user copies a text from a website
2 user pastes it into a msword document
3.1 the text has a transparent img in it, when the user pastes it into msword, msword loads the img from network, deanonimizing ...Let's consider a simple scenario
1 user copies a text from a website
2 user pastes it into a msword document
3.1 the text has a transparent img in it, when the user pastes it into msword, msword loads the img from network, deanonimizing the user.
or
3.2 the text has a transparent swf in it, when the user copies it, the clipboard logger application understands it is a html tryes to render, in order to do it it loads MSIE engine which loads flash plugin which executes swf which collects and sends sensitive data.
TorBrowser must sanitize the info transferred to/from clipboard removing all the content available from the network and all the active content (scripts, swfs, applets, etc).https://gitlab.torproject.org/legacy/trac/-/issues/17570HTTP JavaScript running in Medium-High security mode2020-06-15T23:31:26ZcypherpunksHTTP JavaScript running in Medium-High security modeThis is encrypted because I think it is a serious problem.
I hope I have the right PGP keys for you all, and that you keep them secret keep them safe etc etc!
```
gpg: encrypted with 3072-bit RSA key, ID D2CA27F3F25B8E5E, created 2004-...This is encrypted because I think it is a serious problem.
I hope I have the right PGP keys for you all, and that you keep them secret keep them safe etc etc!
```
gpg: encrypted with 3072-bit RSA key, ID D2CA27F3F25B8E5E, created 2004-07-03
"Nick Mathewson <nickm@alum.mit.edu>"
gpg: encrypted with 4096-bit RSA key, ID 923513C6B0E5067D, created 2015-06-10
"Roger Dingledine <arma@mit.edu>"
gpg: encrypted with 4096-bit RSA key, ID 479AAAF80761B967, created 2012-09-16
"Andrea Shepard (Tor Project key) <andrea@torproject.org>"
gpg: encrypted with 4096-bit RSA key, ID DFC2664D1B749632, created 2013-09-21
"Erinn Clark <erinn@torproject.org>"
gpg: encrypted with 4096-bit RSA key, ID B0D1CB47ACC0A961, created 2015-09-07
"Mike Perry <mikeperry@endarken.info>"
gpg: encrypted with 4096-bit RSA key, ID 57833E6F631602F4, created 2015-07-20
"Georg Koppen <gk@torproject.org>"
gpg: encrypted with 4096-bit RSA key, ID 13E41AB155E052D1, created 2015-09-08
"Isis <isis@torproject.org>"
-----BEGIN PGP MESSAGE-----
hQIMAxPkGrFV4FLRAQ//SwY2nuL+F2FqluJ0e3rS/68hX2XmyYcy+EcR7aPYjGNX
gM6jCwzEpr2ZyW2O8Dq0ZtXtgVZHLIzE0uEinRPwDyVbOX3jyIajlfPKwZ8yxCZF
5laa9wgGJw3PzJc+qPUrlUv0FRbt3CwiQ1puNsNmXMIX5rkUAnWlVr5WfgCI3xU5
ynHd7TUPcwXcJH0k36YXExbLRmT8SrESHYZZxZ0G8+SXYvJYpcqrkirlmYR+8hAw
KfixWlRA2fwbO1yO2q/W1UEfC2xVlU5Mkroh60I0iJPhgPSa3arDOUSSV1fXSveY
9r0g3v7/ltieYBmsUQFGNXRAg5jOu74UiRxNcMBYpQczmYBp6jwpe7R3HzgkWOXC
G1xvvdsIp9xkWGj/C6m7gzmo0tCD98z/ZPG4Rc/rMIL04VBZkaRlB976z9ZvRkzJ
adI5xvXDhxvJGV/BhFHwwpqou3qKkR3niDLST1lJwDwz4e1dFj5VozIBpKzWquhr
O2OxqioIP2KOTDBqLlJiPZNUm4mNOiAqdFTGE7Skl1WTENFTYrQ/qYNZKRQnBGIM
Uk7ObhVjQSyF6PKOk6tJoFwe31Q1B/3VXBnMt9yLN6rf6bBxvSfOn9YfnYIwXQtw
TMeSJIcRBECW8e3IdrXbBmd9KZvK6OWPQtzDhsmKbHxVOJQHKxXK5P595iTf38uF
AgwDV4M+b2MWAvQBD/45mRsa0xkFs8j7XYi7plJtOA86RZtpFXAeVf4EsvN/J+Ti
6rarCT/iZ/kQma7QO96C20zRdaGNCFKCsjKdf5uuTVBpo6ze6ynpf4r800HDA4e8
pKbTxq167zDR6BWcY0FCY3XaeQK82AzKH5MgllIT+wflpyb979p3h+QhioVhMM1c
T/tHxcGeD7h72+ijGoWWpfkg0DRD/XEn2a9C3j3gm2bv5e9XSRGLRrpAVIJKaLXh
cQ/Wo2hiD8JIxWPQC1SnSbrRfUHuUmhvRaZBHnhGaALlSW5x2QqjXflg9yw3dI3P
Nncg1e307wYPfmT0mKll7Y2K3dBr002gIexH8l/BgKQ6LkBTmBRGtyVOejg98h80
15F1Ps/MAcAlPMVQAMIttJHMGCZ6hIPXbjPu9ufNlsSAs6uiKkzWwrtvdUtqPSbL
NdaWzGg/hGhLKsH3SgcE8yzvBLSGrDRrFTMVbWTjnUcYY00dNN9BLsb7fj6CYIR9
bnRCBxUKLv7coB3ZLBK0byfsynUju28fQ2BQhlTbzAs2zmifqVBS1ScNytX0kXwd
QMuVAGpG6PQYmPhGIf1MUmoJ7Ffv1JZADCYLjc7Uhwgvd1mz9Llyl8uQGFIFiGPZ
abDe5itcOy4cIpG7tTzrQHzuSG78THksW0OSkzgGCTjc9xkV9HRegGTbLBVeL4UC
DAOw0ctHrMCpYQEP/R+ELtZSZdYPpXl61nDLLFYqxce4fFv0mySU73wcoJGPNqvU
3xcpusOG45bLTeKNxiUPQ3mbb1fto9Y/1TC4fTjVYuvQTU43mTX/ZQ0JIqJpR1hP
TcSn0UU0gVTuvM1PfseGr7twXPD8y8gQU8oLw5r8CJjCmM3xzzDkC3vpMMTYfquA
nF3EXR4ZJy0jY1DSsfZCOe1znEw8e8555xsmdzkQudxKFMmrhy0MI6mYbX3Nm5KD
0vpCnqZ2G599CzU8dVbd0OScs5oRDZ8JXg9+PkIEq65I1BwGtq+qNs6X78gRdx+6
iqC5ydY9g85ZnlqKrA1M8Nlt7d/HzWIG19LeYtT5mRPZ8zxZmIkWlbldCkgYUfM3
liC9sZ5kKAx1/XibUIHpBPj2vas4i6K3jokkQg6HWcneDe3iaVGHM8BH679pZYSI
IwdxYJDqXhJPBXdB2ITQJFLdStFtCAjiQi1OiNuWnpyVX7jKkMqvGovfjvvIkoE3
5h11QySkKAwAky2YZae4QeEryvk6S8GqMiOrElA98tZF+qH0ZvVe33fD4zGFGEYL
6s7KewzyL0Us8NurWYDdAS+uSyagv501MRmroSYpLHSJG65huRiN6QsmzXmwhdcP
s3toA2BzE3s/7jUpY77MCDf7FpQvEDvji6Qxl0MtqbaFAWuBFJZssStN4Kg3hQIM
A9/CZk0bdJYyAQ//SBOVlk7AQn+wtl0nMoA81rDXGLsACoJOw/UTDdxy5aFAYT5r
HI7g2vkGqCEyP3Y68kGN0Tdp3eEPTnyQd6i0VpcIou55qAGnfl7i1hqYpfHL1eUn
uVToGarTjMuKnpA9Zo1ERWbor4OLRIGMIv+5CFV36aMrb2Sq7M7KiO4ckolXXWH/
Rg5jRYRB4KlKqiLG+51ccGtFmk6jCkhLYVMuqT9ABn7L3aqKJ2GkxHMZFvuekdSZ
DDpHF9mospgK4mRMjZmkL44GXrtEMFiVvBLiLcuWXBEANZKzn1arrTdZLfPs7Kka
rgTFxtKNabnGNrTu4ttNUHDGx65eWUX9QUnIqUAEJO9qOzdDLE8jN/C4HLrlJish
g+z8TIsYjaEdgvMP2/zKiSPr3UzDFQKL0OBKPYgRD9y7/B5tkfC3C3me3n2Bb5Pc
DwVeLTwzy1jWNVjGvfKYMILqI+7hkEjpx8VpyqDJpE2ghyeAJtgMcV87jRO11jTF
szP2MZREJ4FsjVOQyzlzsVyRTo73//g7MYqVirn1oHQtGfacrqZHnqMciG4UY3sA
ILRtog85dHlN74LzRwH9ozRYlbsr0jVfnwCILM7vlIkCeSK/AI79Xy91PqcU5PRw
DoASI+zaMl8r2IACrfy9t16VaGQrxb3Jh4jnC2sU5mE+5o2m3wNuVcGcZRiFAgwD
R5qq+AdhuWcBD/9hHVa1Ln9gJqqGbkYYxcKnOT/U11yyOQz/0abjtybR9T3o8w+t
a6QdTP/GSHeMOELiHG97+vKl3NNqskfQKJXU0btebNmHw0d65XxzFZlUKA8QLLJI
5CyDCRYlTSeMoL1TdyOXtqIHW83nKp59DEQYynp7vWcY9CXoUXk0xRYKyh97l4Vi
yFwWXTbweXCvbKb6JST4xdVFtV9VjFRHhfOBZ6UM0xuaoKpag3QHAR1b6hJ6Z0xD
ivpxhHoPJfjb6z5y4W+4gq2gXOCVnhdUa0OK8qvHb+Ba1KKNGN/Ofmm+0uo+/OmY
axcUSk+qb1Y5oiuZbiMkS1A0AlogrIZFtb84RRq+EPZgI1HbLL4zq9tYfwoVvKqa
Jx0JuGmJZLzruJCwilv2TM40laOgD7VY+cvOAAHQn+Uwz/3An5UChWHyt6LEQrkT
YsY2BN9i06YkfgLW9AZfeKrIUUYHZOF2xCtuz6Fpf1fVcUE5SDoa2TC13OHyYXA/
aP7ENLo4yKyHjGMFeeed5iy3REWh1N1COR+D8/z/OETY8TDEtjbdNQfvEVGSMAdo
Hx0CDhDUQVI9H28Gn+lrPZtNE4x3nbbEbPMqPmyN/24ttghzy96e5NYNDkIliztZ
J/rbdHeOW5rUxnfhzKL7v5eXJZ8N+qmIBJv9jFSo96y66TblczPSdgG3OIUCDAOS
NRPGsOUGfQEQAM246Vila1+y+PI5KkCk5HBrCSWSNq6O7qGAmX5RREpGSfy5XfQx
plXIUDGbC3OvevvMgliLzgfhY1j57Ats1HtlgxiQn64W2mS46cmCaCwPl4WrJ8zQ
WwN+/VfTrGBR7A0BcqYTCE0Z/DWEmm6xlV+byURaUW4lASoc7fwfsGHGemAQS3Ye
9/GoXhddNJBUvGaVE4Q2ABZpWsgkZH+DlQAjpVXdEUw4AN/dPzS21QoEIReTVO4/
z4OUmwt+iPu98GAZAmfq1gJNvNyLhAAI2yOtptBh76xzy032Ri6Nw+XWW1j3HTxV
Ca8sEuCQ+ZKVR+0buKBMF2ri9OSzLwAUiq7w3DWZKCtMtKTr1ltpXVqS2fuMd+rE
/s9QpHI9pSfHZNi5sU7ssxj/k0tq4yhGGgb3jemaKQ3hiQvPJY662ZAz+P0dMyr6
+a9x5syzfRxhwXgGAjsi7Frye3SXjzg/iTbHfEegv6hbohF+sFARbx7THMd1htWZ
5pMtV7IOeFw9J7SzWP1qBQf8fIB8jxSw+b+OlncqsxyYc0eenhfzQvvq18mwKjvT
VztoYILcAaWJpnLP5TuCW9D4jZaQIn97efFqF43R+AMTBFpyFJn+fmXTk00DTepr
CiLurgAiP6lRSHjVPC1RVHzQMEwRArunBr7WO1SRhb/JxZHMcNjb/bQphQGMA9LK
J/PyW45eAQv/Tc0GaBxTpe6ChzvpPfmgMQKGtNilQYStBqR0lMxAoF5xF+gtP1uF
J9AyjmageKCwkH3vJ40B92ZpndaOmpT12LQ3plMMa0IedZaklzoMKWQV+U7aGiVX
499i2ncKESyIrvqywwpZv4S2ucqeYVmc8x0RD9pTM6u2SMumGhNHuPn/qJZzW7yt
UzQYgdAuJaZVLPt0S2CF22wFESDzI2pQdIbuiO9ZQJp/J2G03ODn5oUtzdU7twfD
Koyqzt52d2IpWdkRrsDzUorLxkPcxMzuzAUvofeq6wJGJeYBLq1cmhpCBg9sViL4
TCGc9C2z/v9WbTPvNRS+LGsGgw4b8pl7tfWxd7VPxxBS4evcqu40T8g4TbLQVTrQ
NXEPJBFjMFPayxsOcxRIJBxOF7gDHCi8eHSW0+fRnBxBTZmhEH55mdBH+jiKh7Rr
1BQDy/8S/W97uN7uwcaz3kRNSaSV5DAo0zHR3g16YQIu0Hx/qf9a/yf9HyO1KNzY
qjNJ/yXbQq0U0ukBMmAfHiVQHPbITpWH5DbKCQtQoZWohhYEqeJGRZzn8eNTjvov
lKiGB6uz2vy6J+5qq3GQYLdIdZOMi7mdC5iNUBKrq86dr4fWxR6RfBC/nlL6VqZV
iv64Mn82gt6ITkSYE9+yoF4YgAUeCdhfZIoXtcQnQC4d8VVQOiSB+DeIXWUVC5IG
shWkrdg65EVnBf+c4/SxheFyE2olls79HlJHafxJNw+Uv/ze/utH79LMsF/eRz3m
LSoS4ke487t9p/SyXHRlwodjotgx1hx1dBq8cFx0pYufQQcxTxfeDBIPTW5RufTH
qp0hf3Ivr5yPo4pj2rfR7wkEJb4Osjg4cTxvh85vtKYxj6VZCV3h8t1dBDu9UtX1
FViM/BVAYHH5yg1IJ/CGX2V76LX4bv8jhZkwc7MUjaF+Xs1LkOGm7P7ANFlBDdU+
WVsOkWIoGo+zCnRnbSzKJc3wcLLA1+h7ebOC4QXMSme61on8V12dbYF0gS/nUHs6
g6nzmuR+2nFqKMEO0nN4X5yGbeORFgbSY/gqtcNgrgDXuV4OMc3jqyRHrAp2fJ8J
ze4nxqOlTdLIT/cUU/kF44n35UmRKjV/TiDjTAnLIpuCbSQsZ3BPeo1SHVHIPUfW
k3/wOE00Sfn+Dnctq6VeJwOqoO6OEpUczwU5zeIQwLqX1VH01R61bomGRsD/LLz/
zFcuzm8FIrqThpSFx+KqJyRu9hWpQ/hawi9V1MYOtSNV/gP517/fxgui7GYxD3Ru
zMvxkhDjd5f6cDOW7ksaXhX2m8IZTWEnsxamIrxZNcGcrRPMa6lQ3IIf7WL8VhYO
qjEnzwXd2VlUtgfU3wN+afeFifHf6/J1z5LDv69mtVooI6Xbd7MVThAz/Pio3YNZ
l6r0u5q7cQDL2yzDRyyRFbAsAVdeHzcr/5FB5zkWD63XLAjKnqCw2Za/6UqJtCsL
EFi5U1IBleCK3Hk7kNypCGotJCezZqP8inls/lFKiyi3OraaPdy9OtUIjaCOD0/l
SMwaORozqHSA3MTFoJfpUaJ5ylMhVdqXYI31THbquvDh0iGwAgsn2SwOR4WXeiL9
rjAQrRSZ55+5NnKRYIX8WiikWENHdGOYxm0qHVblqmwUigrymfn4ohocpy64vm63
H8sAsJB/x08LUHMTyBSFslp7g0kIvJSRNE601kXQ7WzoSGUir/9kmECdflSfKHpV
We3Ay1IQKS6nd8TP7DUWsW+EwdfDOirJBjPtl9c+slloorTf3CZwAPN1H5zJWnB/
4m+imh5vuRIzkfjb
=clNe
-----END PGP MESSAGE-----
```https://gitlab.torproject.org/legacy/trac/-/issues/17600HTTPS Everywhere Breaks web page2020-06-13T16:34:22ZTracHTTPS Everywhere Breaks web pageSirs:
I have been using HTTPS Everywhere for about a year in Firefox. Both Firefox, and the addons are set to check for updates automatically, and the following versions are installed on my Windows 7 Pro (32-Bit) PC:
Firefox: 42.0
HTT...Sirs:
I have been using HTTPS Everywhere for about a year in Firefox. Both Firefox, and the addons are set to check for updates automatically, and the following versions are installed on my Windows 7 Pro (32-Bit) PC:
Firefox: 42.0
HTTPS Everywhere: 5.1.1
A website I have been visiting frequently for about 2 years no longer works with HTTPS Everywhere (it formerly did work OK, but as of a few weeks ago no longer displays properly, and has forced me to disable HTTP EVERYWHERE).
Here is a link to a page that fails with HTTPS Everywhere:
https://www.trulia.com/rental/3218486318-38-Hammock-Rd-Clinton-CT-06413
http://www.trulia.com/rental/3218486318-38-Hammock-Rd-Clinton-CT-06413
With HTTPS Everywhere Enabled, both of the above links fail to render the page properly. However, with HTTPS Everywhere Disabled, both links do render the page correctly.
Are there settings I can use to keep HTTPS Everywhere Enabled, that would by-pass certain addresses? That is, in this case, is there a way to set HTTPS Everywhere to be by-passed for all content at www.trulia.com ?
My thanks in advance...
My eMail is: JTG-1112@nyc.rr.com
**Trac**:
**Username**: NYC_hdlWilliam BudingtonWilliam Budingtonhttps://gitlab.torproject.org/legacy/trac/-/issues/17635Assertion due to periodic event initialization being too late.2020-06-13T14:51:10ZYawning AngelAssertion due to periodic event initialization being too late.Reported by Lunar in #tor-dev:
```
Nov 18 12:03:38.000 [err] Bug: /usr/bin/tor(log_backtrace+0x41) [0x5644546256b1] (on Tor 0.2.8.0-alpha-dev )
Nov 18 12:03:38.000 [err] Bug: /usr/bin/tor(tor_assertion_failed_+0x8d) [0x5644546338bd] (on ...Reported by Lunar in #tor-dev:
```
Nov 18 12:03:38.000 [err] Bug: /usr/bin/tor(log_backtrace+0x41) [0x5644546256b1] (on Tor 0.2.8.0-alpha-dev )
Nov 18 12:03:38.000 [err] Bug: /usr/bin/tor(tor_assertion_failed_+0x8d) [0x5644546338bd] (on Tor 0.2.8.0-alpha-dev )
Nov 18 12:03:38.000 [err] Bug: /usr/bin/tor(reschedule_directory_downloads+0x6f) [0x5644545344df] (on Tor 0.2.8.0-alpha-dev )
Nov 18 12:03:38.000 [err] Bug: /usr/bin/tor(learned_bridge_descriptor+0x394) [0x56445461b704] (on Tor 0.2.8.0-alpha-dev )
Nov 18 12:03:38.000 [err] Bug: /usr/bin/tor(routerlist_descriptors_added+0xc3) [0x56445457a4a3] (on Tor 0.2.8.0-alpha-dev )
Nov 18 12:03:38.000 [err] Bug: /usr/bin/tor(router_load_routers_from_string+0x429) [0x56445457db19] (on Tor 0.2.8.0-alpha-dev )
Nov 18 12:03:38.000 [err] Bug: /usr/bin/tor(+0x88089) [0x56445457e089] (on Tor 0.2.8.0-alpha-dev )
Nov 18 12:03:38.000 [err] Bug: /usr/bin/tor(router_reload_router_list+0x26) [0x56445457e0e6] (on Tor 0.2.8.0-alpha-dev )
Nov 18 12:03:38.000 [err] Bug: /usr/bin/tor(do_main_loop+0x118) [0x564454534968] (on Tor 0.2.8.0-alpha-dev )
Nov 18 12:03:38.000 [err] Bug: /usr/bin/tor(tor_main+0x19ad) [0x56445453812d] (on Tor 0.2.8.0-alpha-dev ) Nov 18 12:03:38.000 [err] Bug: /usr/bin/tor(main+0x19) [0x564454530889] (on Tor 0.2.8.0-alpha-dev )
Nov 18 12:03:38.000 [err] Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f9289bd9b45] (on Tor 0.2.8.0-alpha-dev )
Nov 18 12:03:38.000 [err] Bug: /usr/bin/tor(+0x3a8d9) [0x5644545308d9] (on Tor 0.2.8.0-alpha-dev )
```Tor: 0.2.8.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/17650Cannot login to Youtube2020-06-15T23:31:33ZTracCannot login to YoutubeSince a couple of weeks I get this message every time I try to sign into youtube. It used to work fine. Commenting never worked.
"Sorry, we could not log you in at this time. Please try again later."
I even tried with security setting...Since a couple of weeks I get this message every time I try to sign into youtube. It used to work fine. Commenting never worked.
"Sorry, we could not log you in at this time. Please try again later."
I even tried with security setting "Low" and all the check boxes unchecked for the optional security settings.
**Trac**:
**Username**: mansdthttps://gitlab.torproject.org/legacy/trac/-/issues/17674circuit_handle_first_hop doesn't respect ExtendAllowPrivateAddresses2020-06-13T14:55:16Zteorcircuit_handle_first_hop doesn't respect ExtendAllowPrivateAddressescircuit_extend checks ExtendAllowPrivateAddresses, but by then it's too late, we've already connected in circuit_handle_first_hop.
This seems to be a DoS risk.
onionskin_answer handles local connections as a special case using channel_...circuit_extend checks ExtendAllowPrivateAddresses, but by then it's too late, we've already connected in circuit_handle_first_hop.
This seems to be a DoS risk.
onionskin_answer handles local connections as a special case using channel_is_local, so we might actually be making some that serve some useful purpose. (What is that purpose?)
Do we really need to allow connections to our own address from ourselves?
It might be a good idea to refuse to build circuits to ourselves in circuit_handle_first_hop if ExtendAllowPrivateAddresses is 0, and then see what falls over. Unfortunately, this can't be tested using chutney.Tor: 0.2.8.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/17688Our default Guard value is still 3 if no latest consensus or no params2020-06-13T14:51:29ZDavid Gouletdgoulet@torproject.orgOur default Guard value is still 3 if no latest consensus or no params`NumEntryGuards` is a consensus params currently set to `1` which means that we rely on the consensus for the number of entry guards we want. However if tor can't get the "latest consensus" or if that params is not found, the default val...`NumEntryGuards` is a consensus params currently set to `1` which means that we rely on the consensus for the number of entry guards we want. However if tor can't get the "latest consensus" or if that params is not found, the default value is currently `3` (in `decide_num_guards()`):
```
return networkstatus_get_param(NULL, "NumEntryGuards", 3, 1, 10);
```
I wonder why we keep `3` if we decided that `1` was actually more secure?
Important things here I would like to note. We should _NOT_ hardcode default values like this directly in a function call (especially important ones), they should be global defines with a _clear-non-misleading_ name. All of those, the default value, minimum value and maximum value should all be defined in one single location else this is way too error prone in the long run.
If it's indeed a mistake, we should backport this up to 026 I think that is when we set it to one guard.Tor: 0.2.9.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/17702Actually enable ed25519 collation.2020-06-13T14:51:35ZNick MathewsonActually enable ed25519 collation.```
+ if (consensus_method < MIN_METHOD_FOR_ED25519_ID_VOTING + 10/*XXX*/)
```
I think this `+ 10` is debugging code.```
+ if (consensus_method < MIN_METHOD_FOR_ED25519_ID_VOTING + 10/*XXX*/)
```
I think this `+ 10` is debugging code.Tor: 0.2.8.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/17752Null pointer deref in connection_ap_attach_pending()2020-06-13T14:51:50ZDavid Gouletdgoulet@torproject.orgNull pointer deref in connection_ap_attach_pending()My tor client is running on version `0.2.8.0-alpha-dev (git-ee5337e90497e31c)` and I got a crash with a coredump this morning. It happened when one of my hidden service was rebooted and then the torsocks client did try to reconnect.
Las...My tor client is running on version `0.2.8.0-alpha-dev (git-ee5337e90497e31c)` and I got a crash with a coredump this morning. It happened when one of my hidden service was rebooted and then the torsocks client did try to reconnect.
Last notice log:
```
Dec 04 11:39:16.000 [notice] Closing stream for 'SCRUBBED ONION': hidden service is unavailable (try again later).
```
Here is the gdb backtrace of the coredump:
```
[snip]
#3 <signal handler called>
No locals.
#4 connection_ap_attach_pending (retry=retry@entry=1) at src/or/connection_edge.c:801
conn = 0x0
entry_conn_sl_idx = 3
entry_conn_sl_len = 4
entry_conn = 0x0
__FUNCTION__ = "connection_ap_attach_pending"
__func__ = "connection_ap_attach_pending"
#5 0x0000561584871bf4 in connection_ap_rescan_and_attach_pending () at src/or/connection_edge.c:779
entry_conn = 0x561586bcc260
conns = <optimized out>
__FUNCTION__ = "connection_ap_rescan_and_attach_pending"
#6 0x0000561584851da8 in circuit_build_needed_circs (now=now@entry=1449247161) at src/or/circuituse.c:1126
options = 0x561586bcc260
#7 0x00005615847c8288 in run_scheduled_events (now=1449247161) at src/or/main.c:1491
options = 0x561586bcc260
have_dir_info = <optimized out>
i = <optimized out>
[snip]
```
Apparently `conn` is NULL at that point thus this line exploded in`src/or/connection_edge.c`
```
connection_t *conn = ENTRY_TO_CONN(entry_conn);
if (conn->marked_for_close) {
```Tor: 0.2.8.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/17770Buttons on donation banner on about:tor are misaligned sometimes2020-06-15T23:31:43ZGeorg KoppenButtons on donation banner on about:tor are misaligned sometimesAttached is a screen shot I took showing the donation banner with Laura Poitras and the new about:tor lookout for the alpha releases. There are at least two issues:
1) The buttons on the banner are not properly aligned.
2) While testing...Attached is a screen shot I took showing the donation banner with Laura Poitras and the new about:tor lookout for the alpha releases. There are at least two issues:
1) The buttons on the banner are not properly aligned.
2) While testing not only clicking on the buttons led to the donation page but this happened as well if I clicked somewhere on the banner and even if I clicked somewhere outside of it next to it. While I could live with the second case (although I think we should only go to the donation page if one clicks on the buttons) I am against the behavior in the third case: if one is not clicking on the buttons (banner) one does probably not want to donate and we should respect that.
2a) Probably related there is a little area on the left side next to the banner which seems to have focus as well.https://gitlab.torproject.org/legacy/trac/-/issues/17772We don't consider the Guard flag when picking a directory guard2020-06-13T14:51:56ZRoger DingledineWe don't consider the Guard flag when picking a directory guardBack in Tor 0.2.3, when we wanted a new guard, we ended up calling
```
node = choose_good_entry_server(CIRCUIT_PURPOSE_C_GENERAL, NULL);
```
which called
```
choice = router_choose_random_node(excluded, options->ExcludeNodes, flags...Back in Tor 0.2.3, when we wanted a new guard, we ended up calling
```
node = choose_good_entry_server(CIRCUIT_PURPOSE_C_GENERAL, NULL);
```
which called
```
choice = router_choose_random_node(excluded, options->ExcludeNodes, flags);
```
with flags that included CRN_NEED_GUARD, meaning that inside router_choose_random_node(), when it called
```
router_add_running_nodes_to_smartlist(sl, allow_invalid,
need_uptime, need_capacity,
need_guard, need_desc);
```
we would check
```
if (node_is_unreliable(node, need_uptime, need_capacity, need_guard))
continue;
```
In sum, we would avoid considering relays that didn't have the Guard flag, when picking a new guard.
However, starting with Tor 0.2.4, the logic inside add_an_entry_guard() is now:
```
} else if (!for_directory) {
node = choose_good_entry_server(CIRCUIT_PURPOSE_C_GENERAL, NULL);
if (!node)
return NULL;
} else {
const routerstatus_t *rs;
rs = router_pick_directory_server(MICRODESC_DIRINFO|V3_DIRINFO,
PDS_FOR_GUARD);
[...]
}
```
You would think router_pick_directory_server() would look at PDS_FOR_GUARD and choose to avoid relays that don't have the Guard flag. Alas, the only use of for_guard in this function is:
```
if (for_guard && node->using_as_guard)
continue; /* Don't make the same node a guard twice. */
```
I think we need to add another clause into this "if it's unsuitable, continue" list inside router_pick_directory_server_impl().
Right now this bug bites us because the first thing a bootstrapping Tor client does is fetch dir info, so that's when it notices it doesn't have enough guards, so the first three guards it picks are picked via router_pick_directory_server(), and then later when we want to use a guard for a normal circuit, we already find that we have workable guards.
In particular, the bug went in with commit 0c4210f (which looks like it went into 0.2.4.8-alpha).
Now, a separate issue here is that Nick and I were both under the impression that a client will avoid using one of its guards if it loses the Guard flag. That appears to not be happening here either. I'll leave that for a separate bug. :)
Thanks to Mohsen Imani for discovering and reporting!Tor: 0.2.7.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/17782Relays may publish descriptors with incorrect IP address2020-06-13T14:52:02ZfkRelays may publish descriptors with incorrect IP addressI suspect that the following bug could be used by malicious directories
to cause relays that rely on directories to get their external IP address
to publish bogus descriptors which should reduce their chances to make
it into the next con...I suspect that the following bug could be used by malicious directories
to cause relays that rely on directories to get their external IP address
to publish bogus descriptors which should reduce their chances to make
it into the next consensus.
I privately reported the issue yesterday and it has been decided
that there's no need to keep it secret.
The relay elektrobier2 (3D615DEF97F387631F50201FAFA6E7B67FDF3FEF)
is running in an ElectroBSD jail with:
ORPort 9001 NoAdvertise
ORPort 443 NoListen
Tor binds to 127.0.1.1:9001, pf is forwarding incoming traffic
from 95.211.138.7:443 and nat'ing outgoing traffic:
```
[fk@elektrobier ~]$ jls | grep elektrobier2
5 127.0.1.1 elektrobier2 /usr/jails/elektrobier2
[fk@elektrobier ~]$ sudo pfctl -sn -P | grep 127.0.1.1
nat on bge0 inet from 127.0.1.1 to any -> 95.211.138.7
rdr pass on bge0 inet proto tcp from any to 95.211.138.7 port = 443 -> 127.0.1.1 port 9001
```
This used to work fine and Tor correctly detected the external IP
address when the system only had one external IPv4 address.
After the system got a second external IP address, pf was briefly
nat'ing outgoing traffic using both external IPv4 addresses while
still only forwarding incoming traffic from 95.211.138.7:443 to Tor.
This resulted in undesirable behaviour:
```
Dec 01 18:34:58.337 [notice] {OR} Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 01 18:34:58.550 [notice] {GENERAL} Tor has successfully opened a circuit. Looks like client functionality is working.
Dec 01 18:34:58.550 [notice] {CONTROL} Bootstrapped 100%: Done
Dec 01 18:36:45.949 [notice] {CONTROL} New control connection opened from 127.0.1.1.
Dec 01 18:41:01.459 [notice] {OR} Performing bandwidth self-test...done.
Dec 01 18:55:26.206 [notice] {GENERAL} Our IP Address has changed from 95.211.138.51 to 95.211.138.7; rebuilding descriptor (source: 144.76.92.46).
Dec 01 18:55:26.274 [notice] {OR} Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 01 19:55:29.426 [notice] {GENERAL} Our IP Address has changed from 95.211.138.7 to 95.211.138.51; rebuilding descriptor (source: 124.6.36.195).
Dec 01 19:55:30.351 [notice] {OR} Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 01 20:15:45.001 [notice] {GENERAL} Our IP Address has changed from 95.211.138.51 to 95.211.138.7; rebuilding descriptor (source: 146.0.32.144).
Dec 01 20:15:47.988 [notice] {OR} Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 01 20:16:35.027 [notice] {GENERAL} Our IP Address has changed from 95.211.138.7 to 95.211.138.51; rebuilding descriptor (source: 171.25.193.9).
Dec 01 20:16:35.367 [notice] {OR} Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 01 20:36:05.053 [notice] {GENERAL} Our IP Address has changed from 95.211.138.51 to 95.211.138.7; rebuilding descriptor (source: 212.51.155.40).
Dec 01 20:36:05.098 [notice] {OR} Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 01 20:56:25.006 [notice] {GENERAL} Our IP Address has changed from 95.211.138.7 to 95.211.138.51; rebuilding descriptor (source: 154.46.204.125).
Dec 01 20:56:25.254 [notice] {OR} Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 01 21:15:33.282 [notice] {GENERAL} Our IP Address has changed from 95.211.138.51 to 95.211.138.7; rebuilding descriptor (source: 50.7.184.58).
Dec 01 21:15:33.756 [notice] {OR} Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 01 21:16:34.015 [notice] {GENERAL} Our IP Address has changed from 95.211.138.7 to 95.211.138.51; rebuilding descriptor (source: 193.23.244.244).
Dec 01 21:16:34.033 [notice] {OR} Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 01 21:17:35.514 [notice] {GENERAL} Our IP Address has changed from 95.211.138.51 to 95.211.138.7; rebuilding descriptor (source: 208.83.223.34).
Dec 01 21:17:35.710 [notice] {OR} Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 01 21:56:14.079 [notice] {GENERAL} Our IP Address has changed from 95.211.138.7 to 95.211.138.51; rebuilding descriptor (source: 89.46.101.181).
Dec 01 21:56:14.414 [notice] {OR} Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 01 21:57:25.355 [notice] {GENERAL} Our IP Address has changed from 95.211.138.51 to 95.211.138.7; rebuilding descriptor (source: 185.11.136.211).
Dec 01 21:57:25.409 [notice] {OR} Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
```
The messages seem to imply that Tor is only publishing the IP address
after verifying that it can be reached through it.
Unless I misinterpret the code, it only verified that it got incoming traffic
on its ORPort, though, and in this case all the traffic came through
95.211.138.7:443 while traffic to 95.211.138.51:443 was not forwarded to
this relay and not part of the reachability test.
Therefore I suspect that the contacted directories could trick the relay
into publishing any IP address in which case the relay could fall
out of the next consensus.
BTW, after noticing the issue I changed the pf configuration to use a fixed
IP address mapping when nat'ing Tor traffic, but surprisingly this did
not completely workaround the problem for this relay and just reduced
the number of times address changes were detected. Even days later I got:
```
Dec 07 07:00:00.725 [notice] {ACCT} Configured hibernation. This interval began at 2015-12-07 07:00:00; the scheduled wake-up time was 2015-12-07 07:00:00; we expect to exhaust our quota for this interval around 2015-12-08 07:00:00; the next interval begins at 2015-12-08 07:00:00 (all times local)
Dec 07 10:23:30.725 [notice] {GENERAL} Our IP Address has changed from 95.211.138.7 to 95.211.138.51; rebuilding descriptor (source: 62.210.71.167).
Dec 07 10:23:30.841 [notice] {OR} Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 07 10:23:39.912 [notice] {OR} Performing bandwidth self-test...done.
Dec 07 10:43:52.145 [notice] {GENERAL} Our IP Address has changed from 95.211.138.51 to 95.211.138.7; rebuilding descriptor (source: 104.131.136.238).
Dec 07 10:43:52.737 [notice] {OR} Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 07 11:28:43.311 [notice] {GENERAL} Our IP Address has changed from 95.211.138.7 to 95.211.138.51; rebuilding descriptor (source: 62.210.142.39).
Dec 07 11:28:43.734 [notice] {OR} Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 07 11:45:51.148 [notice] {CIRC} No circuits are opened. Relaxed timeout for circuit 665 (a General-purpose client 1-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. 2 guards are live.
Dec 07 12:05:10.598 [notice] {GENERAL} Our IP Address has changed from 95.211.138.51 to 95.211.138.7; rebuilding descriptor (source: 198.100.155.91).
Dec 07 12:05:10.905 [notice] {OR} Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Dec 07 12:34:54.194 [notice] {HEARTBEAT} Heartbeat: Tor's uptime is 0:29 hours, with 2018 circuits open. I've sent 592.36 GB and received 591.16 GB.
Dec 07 12:34:54.205 [notice] {HEARTBEAT} Heartbeat: Accounting enabled. Sent: 41.50 GB / 1000.00 GB, Received: 41.41 GB / 1000.00 GB. The current accounting interval ends on 2015-12-08 07:00:00, in 18:25 hours.
Dec 07 12:34:54.205 [notice] {HEARTBEAT} Circuit handshake stats since last time: 30713/30713 TAP, 64172/64172 NTor.
Dec 07 12:34:54.205 [notice] {HEARTBEAT} Since startup, we have initiated 0 v1 connections, 3 v2 connections, 10 v3 connections, and 233777 v4 connections; and received 402 v1 connections, 112 v2 connections, 3 v3 connections, and 179033 v4 connections.
```
I finally added "Address 95.211.138.7" to see if this helps, but for the relay
polizei-erziehung (5CE3AD8AD04ADE66C0037A3CF5F7F7A40D48A20B) which is running
in another jail on the same system this wasn't necessary and I have no idea why.
While both relays are running 0.2.7.4-rc, other releases should be affected as well.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/17816Buttons on Laura's donation banner are not properly aligned in stable series2020-06-15T23:31:47ZGeorg KoppenButtons on Laura's donation banner are not properly aligned in stable seriesSee attached screen shot. This is with torbutton 1.9.3.6 which should have the fix for #17770. What is worse this issue happens as well if the Tor Browser is up-to-date.See attached screen shot. This is with torbutton 1.9.3.6 which should have the fix for #17770. What is worse this issue happens as well if the Tor Browser is up-to-date.https://gitlab.torproject.org/legacy/trac/-/issues/17829Spoof plugin list2020-06-15T23:31:48ZTracSpoof plugin listAdd spoof plugin list and preferences
## Preferences
plugin.spoof.enable: bool
plugin.spoof.list: str (see example)
## For example:
```
"mimeTypes": [
"description": "Random",
"suffixes": "random",
"...Add spoof plugin list and preferences
## Preferences
plugin.spoof.enable: bool
plugin.spoof.list: str (see example)
## For example:
```
"mimeTypes": [
"description": "Random",
"suffixes": "random",
"type": "application/random"
],
"plugins": [
"application/random": {},
"description": "Random BLah",
"filename": "shaurma.dll",
"version": "454654.077",
"name": "Random",
"length": 1
]
```
**Trac**:
**Username**: hakimhttps://gitlab.torproject.org/legacy/trac/-/issues/17870Some Windows 10 users experience authenticode errors if Tor Browser is signed...2020-06-15T23:33:13ZGeorg KoppenSome Windows 10 users experience authenticode errors if Tor Browser is signed on LinuxThere are users (like the one in https://blog.torproject.org/blog/tor-browser-505-released#comment-141808) that experience authenticode errors when trying to install a Tor Browser signed on a Linux system instead of a Windows one. It wor...There are users (like the one in https://blog.torproject.org/blog/tor-browser-505-released#comment-141808) that experience authenticode errors when trying to install a Tor Browser signed on a Linux system instead of a Windows one. It works fine for me and others on Windows 7, 8 and 10, though.https://gitlab.torproject.org/legacy/trac/-/issues/17874ERROR: AddressSanitizer: heap-use-after-free2020-06-13T14:52:42ZcypherpunksERROR: AddressSanitizer: heap-use-after-free==12345==ERROR: AddressSanitizer: heap-use-after-free on address 0x613000cf5472 at pc 0x55d4620d3245 bp 0x7ffcc0089a50 sp 0x7ffcc0089a48
READ of size 2 at 0x613000cf5472 thread T0
#0 0x55d4620d3244 (/home/cypherpunks/tor-browser_en-...==12345==ERROR: AddressSanitizer: heap-use-after-free on address 0x613000cf5472 at pc 0x55d4620d3245 bp 0x7ffcc0089a50 sp 0x7ffcc0089a48
READ of size 2 at 0x613000cf5472 thread T0
#0 0x55d4620d3244 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xef4244)
#1 0x55d461ef26bb (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xd136bb)
#2 0x55d461ef244f (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xd1344f)
#3 0x55d461dc997e (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xbea97e)
#4 0x55d4619255d2 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x7465d2)
#5 0x55d461917088 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x738088)
#6 0x55d461f23213 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xd44213)
#7 0x55d461f1b081 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xd3c081)
#8 0x55d461d15dd7 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xb36dd7)
#9 0x55d461d4c147 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xb6d147)
#10 0x55d462126fef (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xf47fef)
#11 0x55d4621231f2 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xf441f2)
#12 0x55d46209db6b (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xebeb6b)
#13 0x55d46206a166 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xe8b166)
#14 0x55d4620679cf (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xe889cf)
#15 0x55d46176ef18 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x58ff18)
#16 0x7fb0858abc58 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/libevent-2.1.so.5+0x1fc58)
#17 0x7fb0858a7d01 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/libevent-2.1.so.5+0x1bd01)
#18 0x55d461793edf (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x5b4edf)
#19 0x55d461780a36 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x5a1a36)
#20 0x55d46177c946 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x59d946)
#21 0x55d461786c29 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x5a7c29)
#22 0x55d46176c52a (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x58d52a)
#23 0x7fb0844afb44 (/lib/x86_64-linux-gnu/libc.so.6+0x21b44)
#24 0x55d4616c1216 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x4e2216)
0x613000cf5472 is located 114 bytes inside of 328-byte region [0x613000cf5400,0x613000cf5548)
freed by thread T0 here:
#0 0x55d461747f32 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x568f32)
#1 0x55d462034722 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xe55722)
#2 0x55d46202a6cd (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xe4b6cd)
#3 0x55d46179c7cf (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x5bd7cf)
#4 0x55d4617a0bea (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x5c1bea)
#5 0x55d46179b4c8 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x5bc4c8)
#6 0x55d46176f81d (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x59081d)
#7 0x7fb0858abc58 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/libevent-2.1.so.5+0x1fc58)
previously allocated by thread T0 here:
#0 0x55d461748212 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x569212)
#1 0x55d4625ba9af (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x13db9af)
#2 0x55d4625bac68 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x13dbc68)
#3 0x55d4620264ca (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xe474ca)
#4 0x55d4620280ba (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xe490ba)
#5 0x55d462094402 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xeb5402)
#6 0x55d4620683ca (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xe893ca)
#7 0x55d4620679cf (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0xe889cf)
#8 0x55d46176ef18 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/tor+0x58ff18)
#9 0x7fb0858abc58 (/home/cypherpunks/tor-browser_en-US/Browser/TorBrowser/Tor/libevent-2.1.so.5+0x1fc58)
Shadow bytes around the buggy address:
0x0c2680196a30: fd fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa
0x0c2680196a40: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00
0x0c2680196a50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c2680196a60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c2680196a70: 00 fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
=>0x0c2680196a80: fd fd fd fd fd fd fd fd fd fd fd fd fd fd[fd]fd
0x0c2680196a90: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c2680196aa0: fd fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa
0x0c2680196ab0: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00
0x0c2680196ac0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c2680196ad0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Heap right redzone: fb
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack partial redzone: f4
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
==12345==ABORTING
tor-0.2.7.3-rc-467-ga03469aTor: 0.2.8.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/17875torrc-defaults gets overwritten during update2020-06-15T23:31:51ZTractorrc-defaults gets overwritten during updateAfter updating Tor Browser from 5.0.4 to 5.0.5 recently I noticed that my settings in torrc-defaults have all gone and now I have a fresh config file.
While I understand why keeping old config with new software might not be the best way ...After updating Tor Browser from 5.0.4 to 5.0.5 recently I noticed that my settings in torrc-defaults have all gone and now I have a fresh config file.
While I understand why keeping old config with new software might not be the best way of working, I think it's good to have this file automatically backed up with name like torrc-defaults.orig.1 or similar. May be even give a note on this to user after successful update.
Marked its severity as Major because user can lose all his settings and stay unnoticed until she checks this file later.
**Trac**:
**Username**: Unchquahttps://gitlab.torproject.org/legacy/trac/-/issues/17879Activating the Flash Player is not working anymore since Tor Browser 5.0.52020-06-15T23:31:53ZGeorg KoppenActivating the Flash Player is not working anymore since Tor Browser 5.0.5There are a bunch of users that are complaining about the Flash Player not working anymore e.g. on sites like www.pandora.com. What is going on, I think, is the *detection* being broken which is very likely due to the fix for #17207. The...There are a bunch of users that are complaining about the Flash Player not working anymore e.g. on sites like www.pandora.com. What is going on, I think, is the *detection* being broken which is very likely due to the fix for #17207. The Flash Player itself is still working for me, e.g. on Adobe's test site.
It's unfortunate that this did not get caught in our alpha series but here we are. I guess providing a preference allowing to disable the fix for #17207 might be worth it given that a number of users wouldn't be using Tor Browser otherwise or would be trying to shoot themselves in the foot with having different browsers opened simultaneously.https://gitlab.torproject.org/legacy/trac/-/issues/17895Tor Browser Bundle installer subject to DLL hijacking2020-06-15T23:31:55ZTracTor Browser Bundle installer subject to DLL hijackingtorbrowser-install-5.0.4.exe is vulnerable to DLL hijacking.
Create, e.g. shfolder.dll with a malicious DLL main and observe it runs when the tor installer is executed from the same downloads folder.
http://textslashplain.com/2015/12/1...torbrowser-install-5.0.4.exe is vulnerable to DLL hijacking.
Create, e.g. shfolder.dll with a malicious DLL main and observe it runs when the tor installer is executed from the same downloads folder.
http://textslashplain.com/2015/12/18/dll-hijacking-just-wont-die/
**Trac**:
**Username**: ericlawboklmboklmhttps://gitlab.torproject.org/legacy/trac/-/issues/17901Tor would bind ControlPort to public ip address if it has no localhost interface2020-06-13T14:52:48Zs7rTor would bind ControlPort to public ip address if it has no localhost interfaceFreeBSD jails or some OpenVZ virtual machines do not have a `lo` interace (no 127.0.0.1 or localhost address), they only have an interface with either a public IP address either a NAT address routed upstream on the host.
In this case, i...FreeBSD jails or some OpenVZ virtual machines do not have a `lo` interace (no 127.0.0.1 or localhost address), they only have an interface with either a public IP address either a NAT address routed upstream on the host.
In this case, if ControlPort 9051 is set, it will open the control port on the public IP address without even a warning which is not funny. This applies also to SocksPort, but that's less scary than ControlPort.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/17906Dannenberg's v3ident needs to change2020-06-13T14:52:51ZDamian JohnsonDannenberg's v3ident needs to changeHi Nick. On [#17668](https://trac.torproject.org/projects/tor/ticket/17668#comment:19) I mentioned that Dannenberg's v3ident has changed and this needs to be [updated in config.c](https://gitweb.torproject.org/tor.git/tree/src/or/config....Hi Nick. On [#17668](https://trac.torproject.org/projects/tor/ticket/17668#comment:19) I mentioned that Dannenberg's v3ident has changed and this needs to be [updated in config.c](https://gitweb.torproject.org/tor.git/tree/src/or/config.c#n899). Trivial change, but this should be corrected soonish since due to it Dannenberg isn't taking part in the consensus...
```
from stem.descriptor import DocumentHandler
from stem.descriptor.remote import DescriptorDownloader
downloader = DescriptorDownloader()
print("Consensus is signed by...\n")
query = downloader.get_consensus(document_handler = DocumentHandler.BARE_DOCUMENT)
for authority in query.run()[0].directory_authorities:
print(' * %s with the v3ident of %s' % (authority.nickname, authority.v3ident))
```
```
% python scrap.py
Consensus is signed by...
* tor26 with the v3ident of 14C131DFC5C6F93646BE72FA1401C02A8DF2E8B4
* longclaw with the v3ident of 23D15D965BC35114467363C165C4F724B64B4F66
* maatuska with the v3ident of 49015F787433103580E3B66A1707A00E60F2D15B
* urras with the v3ident of 80550987E1D626E3EBA5E5E75A458DE0626D088C
* moria1 with the v3ident of D586D18309DED4CD6D57C18FDB97EFA96D330566
* dizum with the v3ident of E8A9C45EDE6D711294FADF8E7951F4DE6CA56B58
* gabelmoo with the v3ident of ED03BB616EB2F60BEC80151114BB25CEF515B226
* Faravahar with the v3ident of EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97
```
Again, trivial change. Andreas sent a signed email to dir-auth@ on November 18...
```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello.
The new v3ident for dannenberg is
'0232AF901C31A04EE9848595AF9BB7620D4C5B2E'.
Best
Andreas
-----BEGIN PGP SIGNATURE-----
Comment: Someone you trust is one of us.
iQIcBAEBCAAGBQJWTL7WAAoJECXskyqUhQcxB6IP/3K61NqgLbczZPydJfdxiTFK
OYbQn4j6Q4i3eIHBEyvqSgwEwMmlOe5cxJy/ean+mOyNmgqRUqJxIRQa/7ASmtqA
o/exZI/MKfCltZoSRCk1t1fBYUAlyToI7DLiA0hGBmeVkat9wlkRQUQD3N8XklAh
vJeix9CeIgbkpXxo6p7zmue9NZ2VtkCMJvHn0OmXzrzZIvE6X+uXyEhr/VDOzCnF
hVenqfGzSOP66xiG+b5aXavPjMj/1siw5cItq0CBsz33hL0O1/a/IlrUDhIjcspK
AfBBxmf4rZD0249UpvGoANebRaa+0PVfTqQXzntP4NqXSG6z0O/0bMLvj2Hf1xct
CKhhvSaIUFFru902U81ADnXSgbEDmeDVA9pfi17fJbLoRxAdOElDY3nw8YHGw3+n
FrmUKlZdw9hdEb9N6RXHfTN+NySjxXIz96Pirjt5WuaQ8GWeEislaWgLDuu+7nki
kg6zkmk3qA+i2818aasdN1HSSkuNIYp8NRGf8o6y1HiUdcFnMK2ZybPJfrOT2mUO
znLOPtarnqfdk7itOjMZnyR75URGDRFA0vNt7AWAuMhxrW8K1qz3q+wUS7lmBRCc
GeKE/OS4NSehTp2CWm48mm8BlO2ydHLg0G84oSTQpZAbPsfOBhg+aDKzJsi44lU8
YRb8Ii9mpPrCAu3QTSIX
=j8XS
-----END PGP SIGNATURE-----
```Tor: 0.2.8.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/17915https everywhere breaks videos on foxnews.com2020-06-13T16:34:24Zcypherpunkshttps everywhere breaks videos on foxnews.comVideos on foxnews.com will not play when the extension is enabled.Videos on foxnews.com will not play when the extension is enabled.William BudingtonWilliam Budingtonhttps://gitlab.torproject.org/legacy/trac/-/issues/17958During logon into this trac over Tor - recaptcha hell2020-06-13T16:50:38ZTracDuring logon into this trac over Tor - recaptcha hellI just tried to log into my account on this trac with Torbrowser, and I got an endless series of recaptcha challenges even though I answered them correctly.
**Trac**:
**Username**: zooko2I just tried to log into my account on this trac with Torbrowser, and I got an endless series of recaptcha challenges even though I answered them correctly.
**Trac**:
**Username**: zooko2Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/17968Orbot fails to start with `java.io.FileNotFoundException: armeabi/tor.mp3`2018-12-12T05:26:20ZTracOrbot fails to start with `java.io.FileNotFoundException: armeabi/tor.mp3`I'm trying to use Orbot on two Android devices. One is a Nexus 9 running stock Android 5.0.2, and the other is a Nexus 6P running the nightly build of CyanogenMod 13 (based on Android 6.0.1), built 12/13/2015. Orbot 15.0.1-RC-3-PIE (Tor ...I'm trying to use Orbot on two Android devices. One is a Nexus 9 running stock Android 5.0.2, and the other is a Nexus 6P running the nightly build of CyanogenMod 13 (based on Android 6.0.1), built 12/13/2015. Orbot 15.0.1-RC-3-PIE (Tor 0.2.6.10) is installed from F-Droid on both devices.
When I start Orbot on either of these devices, I get the same exception - something about not being able to find tor.mp3. Here's the log, which is identical on both devices:
```
checking binary version: null
upgrading binaries to latest version: 0.2.6.10
There was an error installing Orbot binaries
Orbot is starting…
Orbot is starting…
checking binary version: null
upgrading binaries to latest version: 0.2.6.10
Unable to start Tor: java.io.FileNotFoundException: armeabi/tor.mp3
Set background service to FOREGROUND
TorService is shutting down
Orbot is deactivated
Orbot is starting…
Orbot is starting…
checking binary version: null
upgrading binaries to latest version: 0.2.6.10
Unable to start Tor: java.io.FileNotFoundException: armeabi/tor.mp3
Set background service to FOREGROUND
TorService is shutting down
Orbot is deactivated
```
I suspect what's happening is that both of these devices have newer architectures and for some reason tor.mp3 is getting put in some architecture-specific location. But I'm really not enough of an expert to tell for sure.
**Trac**:
**Username**: strugeeNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/17979CollecTor downloader module2019-08-17T21:04:59ZDamian JohnsonCollecTor downloader moduleCollecTor added [machine parse-able indexes](https://trac.torproject.org/projects/tor/ticket/17321) to enable Stem (and others) to crawl its contents. We should take advantage of this!CollecTor added [machine parse-able indexes](https://trac.torproject.org/projects/tor/ticket/17321) to enable Stem (and others) to crawl its contents. We should take advantage of this!Damian JohnsonDamian Johnsonhttps://gitlab.torproject.org/legacy/trac/-/issues/17980Torify/Torsocks - Possible bug with OSX's default curl binary2020-06-13T16:09:43ZTracTorify/Torsocks - Possible bug with OSX's default curl binaryOSX default curl binary is not being torified when using _torify_ or _torsocks_. Using: ` curl --proxy socks5h://curl:curl@127.0.0.1:9050/` works fine, however, running ` torify/torsocks curl <url> ` does not work.
Example:
` $ torify ...OSX default curl binary is not being torified when using _torify_ or _torsocks_. Using: ` curl --proxy socks5h://curl:curl@127.0.0.1:9050/` works fine, however, running ` torify/torsocks curl <url> ` does not work.
Example:
` $ torify curl ifconfig.co/all.json # returns original IP `
` $ curl --proxy socks5h://curl:curl@127.0.0.1:9050/ ifconfig.co/all.json # returns the expected output `
` $ torify curl https://check.torproject.org/ | grep -i congratulations # returns nothing`
Torify does work on the Homebrew's curl version with the torify command, but it does not work when running a torify --shell (nor does the default OSX's curl):
{{{
$ torify --shell
/usr/local/bin/torsocks: New torified shell coming right up...
$ /usr/local/opt/curl/bin/curl ifconfig.co/all.json # returns my real IP
$ /usr/bin/curl ifconfig.co/all.json # returns my real IP
$ wget ifconfig.co/all.json # returns my real IP too (using homebrew's wget version 1.17.1)
}}}
OSX default curl:
```
$ curl --version
curl 7.43.0 (x86_64-apple-darwin15.0) libcurl/7.43.0 SecureTransport zlib/1.2.5
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz UnixSockets
```
Homebrew's curl version:
```
$ /usr/local/opt/curl/bin/curl --version
curl 7.46.0 (x86_64-apple-darwin15.0.0) libcurl/7.46.0 SecureTransport zlib/1.2.5
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: IPv6 Largefile NTLM NTLM_WB SSL libz UnixSockets
```
Apple makes this difficult to debug and find out why, due it's Security Integrity Protection (executables signed with restricted entitlements), so I copied OSX's default curl binary to /tmp, ran [1] then I was able to run btruss on the default curl, however I wasn't able run torify with btruss , since [1] didn't work, btruss output didn't have anything interesting as far as I know.
Attachments: with-torify.txt for the output of `sudo torify dtruss ./curl ifconfig.co/all.json` and no-torify.txt for `sudo dtruss ./curl ifconfig.co/all.json`
I am willing to help debug this if needed, but I would like some help to make this easier, since disabling OSX's System Integrity Protection is not a good idea, and apparently code-signing didn't work with me.
[1] ` codesign -f -s `whoami` curl `
'''OSX version: 10.11.2 (15C50)
Torsocks version: Torsocks 2.1.0
Tor version: 0.2.7.6
'''
**Trac**:
**Username**: z0xcdDavid Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/legacy/trac/-/issues/18010Tor Browser 5.0.6 + WIN102020-06-15T23:32:11ZTracTor Browser 5.0.6 + WIN10Im using Tor 5.0.6 on WIN10 64bit,version 1511, build 10586.36 and keyboard doesnt work for typing anything(address, passwords, search,...) but it works for shortcuts(copy, paste, new tab,...)It worked on version 5.0.5, but not after lat...Im using Tor 5.0.6 on WIN10 64bit,version 1511, build 10586.36 and keyboard doesnt work for typing anything(address, passwords, search,...) but it works for shortcuts(copy, paste, new tab,...)It worked on version 5.0.5, but not after latest update. I already tried reinstalling the browser, but no luck. I installed the same verion on brothers laptop which runs WIN10 64bit too and keyboard worked flawleslly.
**Trac**:
**Username**: Loc_doghttps://gitlab.torproject.org/legacy/trac/-/issues/18019Update on non-en-US alpha bundles results in empty dialog being shown2020-06-15T23:32:12ZGeorg KoppenUpdate on non-en-US alpha bundles results in empty dialog being shownIf I update a germen 5.5a5 to 5.5a6 I am greeted with the attached image. There is even no button to cancel this dialog which is pretty confusing. Closing it, though, leads to the changelog being shown.
I guess this dialog pops up in th...If I update a germen 5.5a5 to 5.5a6 I am greeted with the attached image. There is even no button to cancel this dialog which is pretty confusing. Closing it, though, leads to the changelog being shown.
I guess this dialog pops up in the first place because of the do-you-want-to-use-english-for-this-site-question which is supposed to be shown.Mark SmithMark Smithhttps://gitlab.torproject.org/legacy/trac/-/issues/18028Tor 0.2.7.6 uses 100% of CPU all the time!2020-06-13T14:53:20ZTracTor 0.2.7.6 uses 100% of CPU all the time!https://tor.stackexchange.com/questions/9209/tor-0-2-7-6-uses-100-of-cpu-all-the-time
> I just updated my Tor with tor-0.2.7.6.tar.gz, but when I run tor, it uses 100% of one of my CPU's cores, even if I run something simple like tor --...https://tor.stackexchange.com/questions/9209/tor-0-2-7-6-uses-100-of-cpu-all-the-time
> I just updated my Tor with tor-0.2.7.6.tar.gz, but when I run tor, it uses 100% of one of my CPU's cores, even if I run something simple like tor --version. What is going on?
> I use Slackware and used the Tor SlackBuild to build it.
> Try to remove --enable-openbsd-malloc option
> Why would that fix it?
> Because I had a similar problem, and I solved, after some tests, just like that.
**Trac**:
**Username**: cypherpunks-duplicateTor: 0.2.7.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/18042Make sure certificates signed with SHA-1 are not accepted anymore in ESR 452020-06-15T23:32:16ZGeorg KoppenMake sure certificates signed with SHA-1 are not accepted anymore in ESR 45MOzilla released Firefox 43 which did not accept SHA-1 signed certificates anymore. However, this apparently broke some MITM boxes (https://blog.mozilla.org/security/2016/01/06/man-in-the-middle-interfering-with-increased-security/) and ...MOzilla released Firefox 43 which did not accept SHA-1 signed certificates anymore. However, this apparently broke some MITM boxes (https://blog.mozilla.org/security/2016/01/06/man-in-the-middle-interfering-with-increased-security/) and they released a point update reverting this change.
We don't want to have this security feature reverted and should make sure our ESR 45 based code is rejecting SHA-1 signed certificates as expected.https://gitlab.torproject.org/legacy/trac/-/issues/18045Default bowser window is unusably small on Hi-DPI screens2020-06-15T23:32:17ZTracDefault bowser window is unusably small on Hi-DPI screensI use Tor in a removeable pen, sometimes on an ultrabook with a Hi-DPI display 3200x1800, and the browser window is so small that it is unusable - the diagonal of the screen is the equivalent physical size of a 4.5 inch smartphone.
My ...I use Tor in a removeable pen, sometimes on an ultrabook with a Hi-DPI display 3200x1800, and the browser window is so small that it is unusable - the diagonal of the screen is the equivalent physical size of a 4.5 inch smartphone.
My workaround is to:
1) disconnect the ethernet cable
2) maximize the window
3) hit CTRL +++++ (zoom to 300%) so I can read the text
To continue browsing i undo those steps.
I have yet to find a website that this didn't work on, and I have no idea as to why Tor can't simply always tell websites one or two one-size-fits-all browser window sizes, and take the small risk that on some websites the info is going to be disorganized or unreadble. Zooming out or in should fix those few cases. There could even be a way to restore the correct browser window size if the information is distorted.
It would make my life much easier, and would make it much safer. The average user doesn't have the patience to do this to protect their anonimity. It's almost impossible to get through a browsing session without maximizing a window that small, especially when you blow text up so much (200-300% is readable) that the website begins to lose functionality.
thanks for the project, and the hard work. All of us depending on Tor to protect our anonimity, our freedom, and our safety appreciate it.
**Trac**:
**Username**: zorlaguzellikolmazhttps://gitlab.torproject.org/legacy/trac/-/issues/18080CORS header 'Access-Control-Allow-Origin' missing2020-06-15T23:32:24ZcypherpunksCORS header 'Access-Control-Allow-Origin' missingIt seems Tor Browser sometimes strips the Access-Control-Allow-Origin header. I ran into the issue when using Globe. When the header is stripped the browser console contains the warning
```
Cross-Origin Request Blocked: The Same Origin P...It seems Tor Browser sometimes strips the Access-Control-Allow-Origin header. I ran into the issue when using Globe. When the header is stripped the browser console contains the warning
```
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://onionoo.torproject.org/details?lookup=299F0933E93B6571ED1CB3D52090E6E13D62427C. (Reason: CORS header 'Access-Control-Allow-Origin' missing).
```
The reasons why i believe Tor Browser is the cause are
1. Onionoo explicitly sets the [header](https://gitweb.torproject.org/onionoo.git/tree/src/main/java/org/torproject/onionoo/server/ResourceServlet.java#n343).
2. Responses from direct requests to an [Onionoo resource](https://onionoo.torproject.org/summary?limit=4) using Tor Browser sometimes do not show the header in the Network Monitor.
3. Responses from direct requests to the same Onionoo resource using curl consistently contain the header.https://gitlab.torproject.org/legacy/trac/-/issues/18090Torcrazybutton eats all memory and crashes Tor Browser2020-06-16T01:27:53ZbugzillaTorcrazybutton eats all memory and crashes Tor BrowserWhen playing mp4 video not on whitelisted youtube, 2 tabs with videos are opened (autoplay, 'cause Temporary allow for site only by NoScript), one tab is closing by user, switch to another, no response, memory is growing, crash...
The mo...When playing mp4 video not on whitelisted youtube, 2 tabs with videos are opened (autoplay, 'cause Temporary allow for site only by NoScript), one tab is closing by user, switch to another, no response, memory is growing, crash...
The most suspicious component: NoScript (another one string-handling bug?)
Continuing investigation...
Log:
Faulting application name: firefox.exe, version: 38.5.0.0, time stamp: 0x00000000
Faulting module name: mozalloc.dll, version: 38.5.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00001582
Faulting process id: 0xf64
Faulting application path: C:\%REMOVED%\Tor Browser\Browser\firefox.exe
Faulting module path: C:\%REMOVED%\Tor Browser\Browser\mozalloc.dll
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789https://gitlab.torproject.org/legacy/trac/-/issues/18101IP leak from Windows/macOS UI dialog with URI2020-06-15T23:32:34ZTracIP leak from Windows/macOS UI dialog with URIIt is possible for the client IP to leak from the browser and onto the network via the Windows API when prompted with Windows dialog box to select files.
Not entirely sure if this is a bug, but should at least be documented.
Steps to r...It is possible for the client IP to leak from the browser and onto the network via the Windows API when prompted with Windows dialog box to select files.
Not entirely sure if this is a bug, but should at least be documented.
Steps to reproduce:
1. Visit a website that provides an upload box.
2. Instead of selecting a file, paste a URI as a file name.
3. The IP is leaked.
This may potentially work with Ctrl+O (Open File) and Ctrl+S (Save Page As).
Tested on Windows 7 and verified with Wireshark.
**Trac**:
**Username**: uileakArthur EdelsteinArthur Edelsteinhttps://gitlab.torproject.org/legacy/trac/-/issues/18109Orbot with Transparent Proxying breaks Hotspot DHCP2020-06-13T04:54:31ZTracOrbot with Transparent Proxying breaks Hotspot DHCPI'm using the current version of Orbot (15.1.0-RC-2) and CyanogenMod 12.1.
If you enable transparent proxying of all apps ("tor everything"), along with enabling a WiFi hotspot from your phone, any clients attempting to connect to your...I'm using the current version of Orbot (15.1.0-RC-2) and CyanogenMod 12.1.
If you enable transparent proxying of all apps ("tor everything"), along with enabling a WiFi hotspot from your phone, any clients attempting to connect to your phone's hotspot will be unable to get a DHCP lease. It seems it might be involved with the iptables rules that Orbot sets up.
Enabling the option "Tor tethering" doesn't appear to make a difference either. Connecting to the network and then enabling Orbot will cause DNS to stop working.
This means that I cannot effectively both have all of my apps Tor-ified on my phone and also have a wifi-hotspot open for my laptop (even if I'm not trying to tor-ify my laptop's internet).
**Trac**:
**Username**: cypharNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/18116abort in circuitmux_detach_all_circuits on Tor Browser exit with stem scripts...2020-06-13T14:53:36Zteorabort in circuitmux_detach_all_circuits on Tor Browser exit with stem scripts runningUsing master (0.2.8.0-alpha-dev) on OS X I get a crash in circuitmux_detach_all_circuits when I exit Tor Browser (modified to use the binary from a master build) while running a script similar to stem's custom_path_selection.py example.
...Using master (0.2.8.0-alpha-dev) on OS X I get a crash in circuitmux_detach_all_circuits when I exit Tor Browser (modified to use the binary from a master build) while running a script similar to stem's custom_path_selection.py example.
```
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff8d787002 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff96ce75c5 pthread_kill + 90
2 libsystem_c.dylib 0x00007fff9de5f6e7 abort + 129
3 tor 0x00000001036b3e57 circuitmux_detach_all_circuits + 743
4 tor 0x00000001036a0abc channel_free_list + 236
5 tor 0x00000001036a0863 channel_free_all + 147
6 tor 0x0000000103727a43 tor_free_all + 131
7 tor 0x0000000103727cb8 tor_cleanup + 296
8 tor 0x0000000103727262 signal_callback + 2498
9 libevent-2.0.5.dylib 0x0000000103902be0 event_signal_closure + 185
10 libevent-2.0.5.dylib 0x00000001039029f7 event_process_active_single_queue + 237
11 libevent-2.0.5.dylib 0x00000001039030b1 event_process_active + 122
12 libevent-2.0.5.dylib 0x00000001039036ca event_base_loop + 647
13 tor 0x0000000103725aac do_main_loop + 1532
14 tor 0x0000000103727dbf tor_main + 223
15 tor 0x00000001036943a9 main + 25
16 libdyld.dylib 0x00007fff903cb5ad start + 1
```Tor: 0.2.8.x-finalAndrea ShepardAndrea Shepardhttps://gitlab.torproject.org/legacy/trac/-/issues/18150le serveur proxy est introuvable2020-06-15T23:32:41ZTracle serveur proxy est introuvablebonjour,
une fois sur 2 j'ai ce message sur Tor "le serveur proxy est introuvable"
quelle est la solution pour résoudre ce PB
Merci
**Trac**:
**Username**: charly1418bonjour,
une fois sur 2 j'ai ce message sur Tor "le serveur proxy est introuvable"
quelle est la solution pour résoudre ce PB
Merci
**Trac**:
**Username**: charly1418https://gitlab.torproject.org/legacy/trac/-/issues/18167Don't trust "bridge-ips" blindly for user number estimates2020-06-13T18:09:04ZKarsten LoesingDon't trust "bridge-ips" blindly for user number estimatesI think I found a bug in the user number estimates that led to the [confusion on #13171](https://trac.torproject.org/projects/tor/ticket/13171#comment:14).
When I developed the [algorithm for estimating user numbers](https://research.to...I think I found a bug in the user number estimates that led to the [confusion on #13171](https://trac.torproject.org/projects/tor/ticket/13171#comment:14).
When I developed the [algorithm for estimating user numbers](https://research.torproject.org/techreports/counting-daily-bridge-users-2012-10-24.pdf), bridges only reported how many directory requests they responded to (`"dirreq-v3-resp"`), but not how these directory requests were distributed to countries (`"dirreq-v3-reqs"`). What they did report was how many different IP addresses by country connected to the bridge (`"bridge-ips"`). The goal back then was to provide better user numbers per country, so I put in the assumption that the geographic distributions of directory responses and connecting IP addresses would be roughly the same. And I think that assumption is still valid for most cases.
However, the meek version _before_ the #13171 fix broke this assumption. Here's an example from a meek bridge that didn't have this fix yet (descriptor digest `462a2bcc..`):
```
extra-info UtahMeekBridge 88F745840F47CE0C6A4FE61D827950B06F9E4534
published 2015-12-09 22:53:48
dirreq-v3-resp ok=17656,not-enough-sigs=0,unavailable=0,not-found=0,not-modified=6160,busy=0
bridge-ips de=16,cn=8,us=8
```
It's rather unlikely that 17656 responses were sent back to 32 IP addresses or less. Still, following the assumption above, we're saying that half of those 17656 responses were sent back to Germany and one quarter each to China and the U.S.A., and that seems dangerously wrong.
I'm going to attach a scatter plot in a minute, `dirreq-resp-by-bridge-ips-2016-01-27.png`, that puts the numbers of `"dirreq-v3-resp ok=..."` and `"bridge-ips"` in relation for statistics reported between December 1, 2015 and last week. The two meek bridges `88F7..` and `AA03..` stand out quite a bit there as clusters close to the y axis.
I have a few possible fixes in mind. The first part would be to ignore all statistics where 1 unique IP address was reported to make, say, 10 directory requests or more. That would remove all dots to the left of the dashed line in the graph.
The second part of the fix would be to switch from combining `"dirreq-v3-resp"` and `"bridge-ips"` numbers and instead use reported distributions of directory requests to countries (`"dirreq-v3-reqs"`) that were not available 3.5 years ago. But [starting roughly 2 years ago](https://trac.torproject.org/projects/tor/ticket/5824#comment:17), these statistics are being published by more and more bridges.
Here's a descriptor (`fe171d40..`) that was published last week by the same bridge as above, now named `MeekGoogle`, which was after the meek-specific #13171 fix:
```
extra-info MeekGoogle 88F745840F47CE0C6A4FE61D827950B06F9E4534
published 2016-01-22 13:11:10
dirreq-v3-reqs us=7200,ru=1576,de=1520,[..],cn=88,[..]
dirreq-v3-resp ok=22016,not-enough-sigs=0,unavailable=0,not-found=0,not-modified=6016,busy=0
bridge-ips us=3016,ru=632,gb=536,de=528,[..],cn=40,[..]
bridge-ip-versions v4=8752,v6=64
bridge-ip-transports <OR>=8,meek=8808
```
I'm attaching a second scatter plot, `dirreq-resp-by-dirreq-reqs-2016-01-27.png`, that compares the numbers of `"dirreq-v3-resp ok=..."` to `"dirreq-v3-reqs"`. The correlation is close to linear, which makes sense, because the number of directory requests should roughly match the number of directory responses. I think we can make the user number estimates a bit more accurate by making this switch. We would still fall back to `"bridge-ips"` if `"dirreq-v3-reqs"` is empty, but that would mostly affect older statistics.
Part three of the plan would be to remove the `"bridge-ips"` line entirely from little-t-tor, because we wouldn't use it anymore. It's worth noting that we'd lose the ability to filter out meek bridges that don't have the #13171 fix and that don't report usable `"dirreq-v3-reqs"` statistics. Or rather, we wouldn't spot future meek-like bridges affected by a similar bug.
Here's why. The first bridge descriptor above also contained a `"dirreq-v3-reqs"` line that I left out before:
```
extra-info UtahMeekBridge 88F745840F47CE0C6A4FE61D827950B06F9E4534
published 2015-12-09 22:53:48
dirreq-v3-resp ok=17656,not-enough-sigs=0,unavailable=0,not-found=0,not-modified=6160,busy=0
dirreq-v3-reqs us=17648,cn=8
bridge-ips de=16,cn=8,us=8
```
We wouldn't be able to filter out this bridge without the `"bridge-ips"` line. We would have to assume that the vast majority of requests to this bridge came from the U.S.A., and a tiny minority from China.
I think this is acceptable, because the purpose of statistics shouldn't be to validate the correctness of other statistics.
To summarize my plan, here's what I'd like to do:
1. If a bridge reports both a `"dirreq-v3-resp`" and a `"bridge-ips"` line, check if the first number is smaller than 10 times the second number; if not, ignore these directory-request statistics reported by this bridge.
2. If a bridge only reports a `"bridge-ips"` line and no `"dirreq-v3-reqs"` line, assume that the country distributions are the same, which is what we're doing right now.
3. If a bridge reports a `"dirreq-v3-reqs"` line, use that for user number estimates and ignore the `"bridge-ips"` line in case it's present.
Hope this report was not too confusing. Feedback much appreciated.https://gitlab.torproject.org/legacy/trac/-/issues/18168Iframe based AJAX call blocked by popup-blocker or opening in new tab2020-06-15T23:32:44ZTracIframe based AJAX call blocked by popup-blocker or opening in new tabIframe based AJAX call blocked by popup-blocker. After allowing popups, form submits to new tab instead of hidden iframe.
Issue appeared in TBB 5.5. TBB 5.0.7 (previous stable) works with same code normally.
To reproduce go to http:...Iframe based AJAX call blocked by popup-blocker. After allowing popups, form submits to new tab instead of hidden iframe.
Issue appeared in TBB 5.5. TBB 5.0.7 (previous stable) works with same code normally.
To reproduce go to http://dmirrgetyojz735v.onion/d/#set-lang:en and try to make post with JS support enabled.
Code of submit and AJAX handlers can be found in http://dmirrgetyojz735v.onion/js/tinaib1.js , seek doPostForm func.
Trace is like
```
WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate. Use isContentWindowPrivate instead (but only for frame scripts).
pbu_isWindowPrivate@re[/gre/modules/PrivateBrowsingUtils.jsm:25:14](/gre/modules/PrivateBrowsingUtils.jsm:25:14)
nsBrowserAccess.prototype.openURI@chrome://browser/content/browser.js:15194:21
```
Depending of the exact code, call stack may contain func, which actually submitted form.
Tested on Ubuntu 14.04 x64.
**Trac**:
**Username**: sky_kohaiMark SmithMark Smithhttps://gitlab.torproject.org/legacy/trac/-/issues/18171Dlls brokenness with Windows10 Build 142512020-06-15T23:34:54ZTracDlls brokenness with Windows10 Build 14251I installed InsiderPreview Build 14251, and restart Machine.
Tor did not start.
I will attach the fault log XML.
**Trac**:
**Username**: Coh_tI installed InsiderPreview Build 14251, and restart Machine.
Tor did not start.
I will attach the fault log XML.
**Trac**:
**Username**: Coh_thttps://gitlab.torproject.org/legacy/trac/-/issues/18200TrackHostExits forces circuits to same exit, regardless of SOCKSPort isolatio...2020-06-13T14:53:54ZcypherpunksTrackHostExits forces circuits to same exit, regardless of SOCKSPort isolation flagsI've noticed that adding the line
> TrackHostExits .
interferes with
> SOCKSPort 9050 IsolateClientProtocol IsolateSOCKSAuth
> SOCKSPort 9060 IsolateClientProtocol IsolateSOCKSAuth
and possibly other isolation flags.
Steps to reproduce:...I've noticed that adding the line
> TrackHostExits .
interferes with
> SOCKSPort 9050 IsolateClientProtocol IsolateSOCKSAuth
> SOCKSPort 9060 IsolateClientProtocol IsolateSOCKSAuth
and possibly other isolation flags.
Steps to reproduce:
1. Disable TrackHostExits
2. Run two Tor Browser instances pointed at different SOCKSPorts, or run twice `torsocks curl https://check.torproject.org` with IsolatePID=1. You should get two different exit IPs.
3. Enable TrackHostExits and repeat step 2. You will get the same IP accross different Tor Browser instances using different SOCKSPorts, or two instances of torsocks even when IsolatePID=1.
Expected result:
With TrackHostExits, Tor should track the host exit node within the scope of the client SOCKSPort (IsolateClientProtocol) and in compliance with other isolation flags. That is, 127.0.0.1:9050 to check.torproject.org should use the same exit until TrackHostExitsExpire, but should NOT use that same exit for 127.0.0.1:9060 to check.torproject.org if IsolateClientProtocol is enabled. The same should go for IsolateSOCKSAuth (used by torsocks IsolatePID=1), but for the SOCKS username and password rather than port, and all other isolation flags based on their respective criteria.
Note, from the Torrc manual page:
>IsolateClientProtocol
>Don’t share circuits with streams using a different protocol. (SOCKS 4, SOCKS 5, TransPort connections, NATDPort connections, and DNSPort requests are all considered to be different protocols.)
Although TransPort 9040 and SOCKSPort 9050 are different protocols subject to isolation from one another, the language does not make it completely clear whether SOCKSPort 9050 is different from SOCKSPort 9060, for example. In my testing, different SOCKSPorts **do** seem to be treated as different protocols, subject to isolation when TrackHostExits is disabled. Even if they are considered the same protocol, not subject to isolation, this doesn't explain why unique SOCKS usernames/passwords are not isolated.
Actual result:
With TrackHostExits enabled, Tor appears to share circuits to the same exit across all combinations of SOCKSPorts and SOCKS username/password combinations. This effectively negates the effects of IsolatePID=1 and the "New Tor circuit for this site" button in Tor Browser, as well as Tor Browsers connecting on different SOCKSPorts, and possibly violates all other isolation flags.
Use cases:
* Using multiple Tor Browsers on different SOCKSPorts that all use the system-installed Tor, or the same instance of the user-installed Tor. Ideally the user should be able to simultaneously take advantage of:
* Browser-level (cache, etc) isolation between instances of Tor Browser.
* Circuit-level exit isolation between those instances.
* TrackHostExits within, but not between, those instances, in cases where sites expire authentication cookies when the exit changes.
* Using the "New Tor circuit for this site" button in Tor Browser.
* Using IsolatePID=1 with torsocks. Long lived applications should be able to reuse exits until TrackHostExitsExpire, but NOT share them with other PIDs.
Workarounds:
* Run multiple instances of Tor.
* Requires multiple users, or some kind of chroot, in order to work around hardcoded paths, and manual torrc/browser port configuration. Running multiple instances of Tor as the same user is non-trivial.
* Consumes additional bandwidth and machine resources.
* Makes it more difficult to firewall non-Tor traffic using `iptables -m owner --uid-owner "tor"`
* Disable TrackHostExits
* Some sites will expire authentication cookies frequently and require the user to login again. As this is often a security measure, it is not really a bug on the site's part.
* Use the site's .onion address.
* Many sites do not have a .onion address.
Possible fixes:
TrackHostExits in compliance with existing isolation flags, the same way as if TrackHostExits is disabled, as described above.
Alternatively, allow TrackHostExits to be set on a port-by-port basis. E.g.
> SocksPort 9050 IsolateClientProtocol TrackHostExits="."
> SocksPort 9060 IsolateClientProtocol TrackHostExits="example.org,example.com"
> SocksPort 9070 IsolateClientProtocol
In this example, exit tracking is disabled for 9070, enabled for 9050 and 9060, but Tor should NOT share circuits between 9050 and 9060. This alternative solution is more of an enhancement while the first one is a bug fix.
Not tested:
IsolateClientAddr
IsolateDestAddr
IsolateDestPort
SessionGroupTor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/18209Metrics broken by bogus bandwidth data2020-06-13T18:13:32ZcypherpunksMetrics broken by bogus bandwidth dataThe servers mentioned here show >1000MB/s advertised bandwidth:
https://lists.torproject.org/pipermail/tor-talk/2016-January/040105.html
Metrics show huge anomalies, probably caused by this:
https://metrics.torproject.org/bandwidth-flag...The servers mentioned here show >1000MB/s advertised bandwidth:
https://lists.torproject.org/pipermail/tor-talk/2016-January/040105.html
Metrics show huge anomalies, probably caused by this:
https://metrics.torproject.org/bandwidth-flags.html
https://metrics.torproject.org/advbwdist-relay.html
https://onionoo.torproject.org/details?fingerprint=0ED2D734F295427E5A3719FA7B9985C335839123
{"version":"3.1",
"relays_published":"2016-02-02 09:00:00",
"relays":[
{ "nickname":"dljupiter",
"fingerprint":"0ED2D734F295427E5A3719FA7B9985C335839123",
"first_seen":"2016-01-26 05:00:00","running":false,
"flags":["Exit","Fast","Running","Stable","Valid"],
"country":"lu","country_name":"Luxembourg",
"consensus_weight":44500,
"bandwidth_rate":1073410156,
"bandwidth_burst":1073325870,
"observed_bandwidth":1073333588,
"advertised_bandwidth":1073325870,
"measured":true,
...
}https://gitlab.torproject.org/legacy/trac/-/issues/18210Tor Browser 5.5 does not start on Ubuntu wily2020-06-13T04:58:34ZTracTor Browser 5.5 does not start on Ubuntu wilySince the Update to TBB 5.5, I only get "Tor unexpectedly exited" when starting. The only error I find in the logs is
/home/doirya/.local/opt/tor-browser_en-US/Browser/TorBrowser/Tor/tor: symbol lookup error: /home/doirya/.local/opt/t...Since the Update to TBB 5.5, I only get "Tor unexpectedly exited" when starting. The only error I find in the logs is
/home/doirya/.local/opt/tor-browser_en-US/Browser/TorBrowser/Tor/tor: symbol lookup error: /home/doirya/.local/opt/tor-browser_en-US/Browser/TorBrowser/Tor/tor: undefined symbol: evutil_secure_rng_set_urandom_device_file
This may be related to libevent in ubuntu being only at version 2.0.21, while the function above apparently was added in 2.0.22.
**Trac**:
**Username**: doiryaboklmboklmhttps://gitlab.torproject.org/legacy/trac/-/issues/18213The parameter WarnUnsafeSocks does not work as specified in the documentation...2020-06-13T14:53:57ZTracThe parameter WarnUnsafeSocks does not work as specified in the documentation, no warning is logged in the log fileThe parameter WarnUnsafeSocks does not work as specified in the documentation, no warning is logged in the log file when a connection is done to an ip address.
If WarnUnsafeSocks 1 (default) is set there is no warning in the log file.
I...The parameter WarnUnsafeSocks does not work as specified in the documentation, no warning is logged in the log file when a connection is done to an ip address.
If WarnUnsafeSocks 1 (default) is set there is no warning in the log file.
If you look at the code for log_unsafe_socks_warning, the only case where an error is logged is when safe_socks is true. safe_socks is true only when SafeSocks parameter is set, but not when WarnUnsafeSocks is set.
The code should be
```
if (safe_socks || options->WarnUnsafeSocks) {
```
instead of
```
if (safe_socks) {
```
**Trac**:
**Username**: propropusTor: unspecifiedRoger DingledineRoger Dingledinehttps://gitlab.torproject.org/legacy/trac/-/issues/18236Remove the "Connect now" button2016-02-04T17:11:38ZTracRemove the "Connect now" buttonThis https://i.imgur.com/uLIDGoF.png button is basically a "go to jail" button, it simultaneously logs you into all of your accounts and is very easy to accidentally click. Clicking it will make it very easy for an attacker to connect yo...This https://i.imgur.com/uLIDGoF.png button is basically a "go to jail" button, it simultaneously logs you into all of your accounts and is very easy to accidentally click. Clicking it will make it very easy for an attacker to connect your identities.
**Trac**:
**Username**: seanrosehttps://gitlab.torproject.org/legacy/trac/-/issues/18242Revert no-assertions-on-coverage, or make it controlled by an option.2020-06-13T14:54:02ZNick MathewsonRevert no-assertions-on-coverage, or make it controlled by an option.In 1228dd293b60a we made TOR_COVERAGE equavalent to NDEBUG so that branch coverage could be accurate.
But we hate NDEBUG.
I just spent 20 minutes too long debugging a problem because I'd forgotten that I was building with enable_cover...In 1228dd293b60a we made TOR_COVERAGE equavalent to NDEBUG so that branch coverage could be accurate.
But we hate NDEBUG.
I just spent 20 minutes too long debugging a problem because I'd forgotten that I was building with enable_coverage and that as such I shouldn't expect tor_assert to do anything.
We should either revert 1228dd293b60a, or make an --enable-branch-coverage option for configure that you have to use if you want to do branch coverage this way.Tor: 0.2.8.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/18251circuitmux_detach_all_circuits: Assertion to_remove->muxinfo.policy_data == N...2020-06-13T14:54:04Zs7rcircuitmux_detach_all_circuits: Assertion to_remove->muxinfo.policy_data == NULL failedAfter upgrading from 0.2.8.0 to 0.2.8.1 on a relay. Upgrade or start of 0.2.8.1 (after upgrade) were not affected apparently.
```
Feb 05 13:05:09.000 [notice] Clean shutdown finished. Exiting.
Feb 05 13:05:09.000 [warn] Couldn't find ci...After upgrading from 0.2.8.0 to 0.2.8.1 on a relay. Upgrade or start of 0.2.8.1 (after upgrade) were not affected apparently.
```
Feb 05 13:05:09.000 [notice] Clean shutdown finished. Exiting.
Feb 05 13:05:09.000 [warn] Couldn't find circuit 2642529256 (for channel 924182)
Feb 05 13:05:09.000 [err] tor_assertion_failed_(): Bug: ../src/or/circuitmux.c:501: circuitmux_detach_all_circuits: Assertion to_remove->muxinfo.policy_data == NULL failed; aborting. (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:09.000 [err] Bug: Assertion to_remove->muxinfo.policy_data == NULL failed in circuitmux_detach_all_circuits at ../src/or/circuitmux.c:501. Stack trace: (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:09.000 [err] Bug: /usr/bin/tor(log_backtrace+0x42) [0x7f225673f7c2] (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:09.000 [err] Bug: /usr/bin/tor(tor_assertion_failed_+0x9f) [0x7f225674d48f] (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:09.000 [err] Bug: /usr/bin/tor(circuitmux_detach_all_circuits+0x299) [0x7f22566cb149] (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:09.000 [err] Bug: /usr/bin/tor(+0xae27d) [0x7f22566b827d] (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:09.000 [err] Bug: /usr/bin/tor(channel_free_all+0x8f) [0x7f22566b876f] (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:09.000 [err] Bug: /usr/bin/tor(tor_free_all+0x7f) [0x7f225664d59f] (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:09.000 [err] Bug: /usr/bin/tor(tor_cleanup+0x2c) [0x7f225664d71c] (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:09.000 [err] Bug: /usr/bin/tor(consider_hibernation+0xf9) [0x7f22567386d9] (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:09.000 [err] Bug: /usr/bin/tor(+0x41840) [0x7f225664b840] (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:09.000 [err] Bug: /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5(event_base_loop+0x414) [0x7f2255d18254] (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:09.000 [err] Bug: /usr/bin/tor(do_main_loop+0x225) [0x7f225664c965] (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:09.000 [err] Bug: /usr/bin/tor(tor_main+0x1c5d) [0x7f225665001d] (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:09.000 [err] Bug: /usr/bin/tor(main+0x19) [0x7f2256648749] (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:09.000 [err] Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f2254f35ead] (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:09.000 [err] Bug: /usr/bin/tor(+0x3e799) [0x7f2256648799] (on Tor 0.2.8.0-alpha-dev )
Feb 05 13:05:18.000 [notice] Tor 0.2.8.1-alpha-dev (git-1f5cdf2b6c72ae89+26ab2e0) opening log file.
```Tor: 0.2.8.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/18273CSS animations provide high resolution timer2020-06-15T23:33:10ZcypherpunksCSS animations provide high resolution timerTBB supports CSS animations out of the box (even without Javascript). These animations run smoothly and likely result in at least 60Hz resolution.
All kinds of properties can be animated and can be turned into Javascript events (e.g. us...TBB supports CSS animations out of the box (even without Javascript). These animations run smoothly and likely result in at least 60Hz resolution.
All kinds of properties can be animated and can be turned into Javascript events (e.g. using change events) to create timers.
CSS animation demo:
https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Animations/Using_CSS_animationshttps://gitlab.torproject.org/legacy/trac/-/issues/182743DES_EDE_CBC cipher is weak in the current TBB configuration!2020-06-15T23:33:11Zbugzilla3DES_EDE_CBC cipher is weak in the current TBB configuration!From The Design and Implementation of the Tor Browser [DRAFT]:
> we also enable TLS False Start via the Firefox Pref security.ssl.enable_false_start.
From TLS False Start https://tools.ietf.org/html/draft-bmoeller-tls-falsestart-00
> ge...From The Design and Implementation of the Tor Browser [DRAFT]:
> we also enable TLS False Start via the Firefox Pref security.ssl.enable_false_start.
From TLS False Start https://tools.ietf.org/html/draft-bmoeller-tls-falsestart-00
> generally symmetric ciphers with an effective key length of 128 bits or more can be considered strong. In TLS 1.2 [RFC5246], this allows all cipher suites **except** those using the NULL or 3DES_EDE_CBC ciphers
Detected by https://www.ssllabs.com/ssltest/viewMyClient.html
> TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa) 112
In `about:config`:
`security.ssl3.rsa_des_ede3_sha`;`true`
Why is this security hole still present?https://gitlab.torproject.org/legacy/trac/-/issues/18303Serious and extremely annoying bug2016-02-11T18:57:29ZTracSerious and extremely annoying bugHi, Tor Button have a serious bug. I use Windows 7 x64.
It prevent to maximize the window and freeze screen and display driver. The only page Tor Browser can be maximized is "about:tor" because it set this flag
**extensions.torbutton.st...Hi, Tor Button have a serious bug. I use Windows 7 x64.
It prevent to maximize the window and freeze screen and display driver. The only page Tor Browser can be maximized is "about:tor" because it set this flag
**extensions.torbutton.startup_resize_period** to false
all other pages set the flag to true and start the bug to cause the freeze.
the issue is described here.
https://gitweb.torproject.org/torbutton.git/tree/src/chrome/content/torbutton.js?id=a6f8dcec3bc11bcfc9ded64943051e2408ee9190#n3598
and here
https://trac.torproject.org/projects/tor/ticket/16725
But it is SIX months old.
Really Is it so difficult add a line of code to set the flag to false when the user open a new tab?
I spent half hour EVERY TIME to fix the issue after every system freeze and sometimes I have to reinstall Tor Browser from scratch to solve.
Thank you very much
**Trac**:
**Username**: Blissethttps://gitlab.torproject.org/legacy/trac/-/issues/18331Update OS X toolchain to work with ESR 452020-06-15T23:33:24ZGeorg KoppenUpdate OS X toolchain to work with ESR 45It seems our cross-compiler crashes while trying to compile ESR 45:
```
x86_64-apple-darwin10-clang++ ... /home/ubuntu/build/tor-browser/intl/icu/source/common/umutex.cpp
x86_64-apple-darwin10-clang: SemaChecking.cpp:4431: void {ano...It seems our cross-compiler crashes while trying to compile ESR 45:
```
x86_64-apple-darwin10-clang++ ... /home/ubuntu/build/tor-browser/intl/icu/source/common/umutex.cpp
x86_64-apple-darwin10-clang: SemaChecking.cpp:4431: void {anonymous}::DiagnoseOutOfRangeComparison(clang::Sema&, clang::BinaryOperator*, clang::Expr*, clang::Expr*, llvm::APSInt, bool): Assertion `(OtherT->isIntegerType() && ConstantT->isIntegerType()) && "comparison with non-integer type"' failed.
0 x86_64-apple-darwin10-clang 0x00000000022b6392 llvm::sys::PrintStackTrace(_IO_FILE*) + 34
1 x86_64-apple-darwin10-clang 0x00000000022b67c9
2 libpthread.so.0 0x00002b2aba39bcb0
3 libc.so.6 0x00002b2abb0700d5 gsignal + 53
4 libc.so.6 0x00002b2abb07383b abort + 379
5 libc.so.6 0x00002b2abb068d9e
6 libc.so.6 0x00002b2abb068e42
7 x86_64-apple-darwin10-clang 0x0000000000b2a7d9
8 x86_64-apple-darwin10-clang 0x0000000000b3899e
9 x86_64-apple-darwin10-clang 0x0000000000b38d61 clang::Sema::CheckCompletedExpr(clang::Expr*, clang::SourceLocation, bool) + 33
10 x86_64-apple-darwin10-clang 0x0000000000c8f06a clang::Sema::ActOnFinishFullExpr(clang::Expr*, clang::SourceLocation, bool, bool) + 250
11 x86_64-apple-darwin10-clang 0x0000000000ad5cc5 clang::Parser::ParseWhileStatement(clang::SourceLocation*) + 469
12 x86_64-apple-darwin10-clang 0x0000000000ad108c clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*, 32u>&, bool, clang::SourceLocation*, clang::Parser::ParsedAttributesWithRange&) + 1036
13 x86_64-apple-darwin10-clang 0x0000000000ad159e clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*, 32u>&, bool, clang::SourceLocation*) + 142
14 x86_64-apple-darwin10-clang 0x0000000000ad2217 clang::Parser::ParseCompoundStatementBody(bool) + 1607
15 x86_64-apple-darwin10-clang 0x0000000000ad27dd clang::Parser::ParseCompoundStatement(bool, unsigned int) + 45
16 x86_64-apple-darwin10-clang 0x0000000000ad2832 clang::Parser::ParseCompoundStatement(bool) + 18
17 x86_64-apple-darwin10-clang 0x0000000000ad11fa clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*, 32u>&, bool, clang::SourceLocation*, clang::Parser::ParsedAttributesWithRange&) + 1402
18 x86_64-apple-darwin10-clang 0x0000000000ad159e clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*, 32u>&, bool, clang::SourceLocation*) + 142
19 x86_64-apple-darwin10-clang 0x0000000000ad7216 clang::Parser::ParseIfStatement(clang::SourceLocation*) + 1030
20 x86_64-apple-darwin10-clang 0x0000000000ad138b clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*, 32u>&, bool, clang::SourceLocation*, clang::Parser::ParsedAttributesWithRange&) + 1803
21 x86_64-apple-darwin10-clang 0x0000000000ad159e clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*, 32u>&, bool, clang::SourceLocation*) + 142
22 x86_64-apple-darwin10-clang 0x0000000000ad2217 clang::Parser::ParseCompoundStatementBody(bool) + 1607
23 x86_64-apple-darwin10-clang 0x0000000000ad26c3 clang::Parser::ParseFunctionStatementBody(clang::Decl*, clang::Parser::ParseScope&) + 211
24 x86_64-apple-darwin10-clang 0x0000000000a754cb clang::Parser::ParseFunctionDefinition(clang::ParsingDeclarator&, clang::Parser::ParsedTemplateInfo const&, clang::Parser::LateParsedAttrList*) + 2635
25 x86_64-apple-darwin10-clang 0x0000000000a8153e clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&, unsigned int, bool, clang::SourceLocation*, clang::Parser::ForRangeInit*) + 1902
26 x86_64-apple-darwin10-clang 0x0000000000a70625 clang::Parser::ParseDeclOrFunctionDefInternal(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec&, clang::AccessSpecifier) + 245
27 x86_64-apple-darwin10-clang 0x0000000000a70d68 clang::Parser::ParseDeclarationOrFunctionDefinition(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*, clang::AccessSpecifier) + 1016
28 x86_64-apple-darwin10-clang 0x0000000000a72280 clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) + 96
29 x86_64-apple-darwin10-clang 0x0000000000a932dd clang::Parser::ParseInnerNamespace(std::vector<clang::SourceLocation, std::allocator<clang::SourceLocation> >&, std::vector<clang::IdentifierInfo*, std::allocator<clang::IdentifierInfo*> >&, std::vector<clang::SourceLocation, std::allocator<clang::SourceLocation> >&, unsigned int, clang::SourceLocation&, clang::ParsedAttributes&, clang::BalancedDelimiterTracker&) + 381
30 x86_64-apple-darwin10-clang 0x0000000000a93e1e clang::Parser::ParseNamespace(unsigned int, clang::SourceLocation&, clang::SourceLocation) + 2670
31 x86_64-apple-darwin10-clang 0x0000000000a87d0e clang::Parser::ParseDeclaration(llvm::SmallVector<clang::Stmt*, 32u>&, unsigned int, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&) + 558
32 x86_64-apple-darwin10-clang 0x0000000000a7241b clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) + 507
33 x86_64-apple-darwin10-clang 0x0000000000a98f2b clang::Parser::ParseLinkage(clang::ParsingDeclSpec&, unsigned int) + 1067
34 x86_64-apple-darwin10-clang 0x0000000000a70684 clang::Parser::ParseDeclOrFunctionDefInternal(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec&, clang::AccessSpecifier) + 340
35 x86_64-apple-darwin10-clang 0x0000000000a70d68 clang::Parser::ParseDeclarationOrFunctionDefinition(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*, clang::AccessSpecifier) + 1016
36 x86_64-apple-darwin10-clang 0x0000000000a72280 clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) + 96
37 x86_64-apple-darwin10-clang 0x0000000000a729b8 clang::Parser::ParseTopLevelDecl(clang::OpaquePtr<clang::DeclGroupRef>&) + 184
38 x86_64-apple-darwin10-clang 0x0000000000a6c00d clang::ParseAST(clang::Sema&, bool, bool) + 493
39 x86_64-apple-darwin10-clang 0x00000000007650ea clang::FrontendAction::Execute() + 282
40 x86_64-apple-darwin10-clang 0x0000000000748ddd clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) + 349
41 x86_64-apple-darwin10-clang 0x000000000072fb52 clang::ExecuteCompilerInvocation(clang::CompilerInstance*) + 1666
42 x86_64-apple-darwin10-clang 0x0000000000728c18 cc1_main(char const**, char const**, char const*, void*) + 1224
43 x86_64-apple-darwin10-clang 0x000000000070d9e1 main + 705
44 libc.so.6 0x00002b2abb05b76d __libc_start_main + 237
45 x86_64-apple-darwin10-clang 0x00000000007285dd
Stack dump:
0. Program arguments: /home/ubuntu/build/x-tools/x86_64-apple-darwin10/bin/x86_64-apple-darwin10-clang -cc1 -triple x86_64-apple-macosx10.6.0 -isysroot /home/ubuntu/build/MacOSX10.7.sdk -emit-obj -disable-free -main-file-name umutex.cpp -mrelocation-model pic -pic-level 2 -mdisable-fp-elim -relaxed-aliasing -masm-verbose -munwind-tables -target-cpu core2 -target-linker-version 2.22 -coverage-file /home/ubuntu/build/tor-browser/obj-macos/intl/icu/target/common/umutex.o -resource-dir /home/ubuntu/build/x-tools/x86_64-apple-darwin10/bin/../lib/clang/3.3 -dependency-file umutex.d -MT umutex.d umutex.o umutex.o -isysroot /home/ubuntu/build/MacOSX10.7.sdk -D U_ATTRIBUTE_DEPRECATED= -D U_COMMON_IMPLEMENTATION -D U_USING_ICU_NAMESPACE=0 -D U_NO_DEFAULT_INCLUDE_UTF_HEADERS=1 -D UCONFIG_NO_LEGACY_CONVERSION -D UCONFIG_NO_TRANSLITERATION -D UCONFIG_NO_REGULAR_EXPRESSIONS -D UCONFIG_NO_BREAK_ITERATION -D U_CHARSET_IS_UTF8 -D U_HAVE_ATOMIC=0 -D DEFAULT_ICU_PLUGINS="/usr/local/lib/icu" -D NO_X11 -U DEBUG -D NDEBUG -D U_STATIC_IMPLEMENTATION -I /home/ubuntu/build/tor-browser/intl/icu/source/common -I /home/ubuntu/build/tor-browser/intl/icu/source/i18n -I /home/ubuntu/build/tor-browser/intl/icu/source/common -I/home/ubuntu/build/x-tools/x86_64-apple-darwin10/lib/gcc/x86_64-apple-darwin10/5666.3/../../../../x86_64-apple-darwin10/include/c++/5666.3 -I/home/ubuntu/build/x-tools/x86_64-apple-darwin10/lib/gcc/x86_64-apple-darwin10/5666.3/../../../../x86_64-apple-darwin10/include/c++/5666.3/x86_64-apple-darwin10 -I/home/ubuntu/build/x-tools/x86_64-apple-darwin10/lib/gcc/x86_64-apple-darwin10/5666.3/../../../../x86_64-apple-darwin10/include/c++/5666.3/backward -I/home/ubuntu/build/x-tools/x86_64-apple-darwin10/lib/gcc/x86_64-apple-darwin10/5666.3/include -I/home/ubuntu/build/x-tools/x86_64-apple-darwin10/lib/gcc/x86_64-apple-darwin10/5666.3/include-fixed -I/home/ubuntu/build/x-tools/x86_64-apple-darwin10/lib/gcc/x86_64-apple-darwin10/5666.3/../../../../x86_64-apple-darwin10/include -O3 -Wall -Wempty-body -Woverloaded-virtual -Wsign-compare -Wwrite-strings -Wno-invalid-offsetof -Wno-c++0x-extensions -Wno-extended-offsetof -Wno-unknown-warning-option -Wno-return-type-c-linkage -std=gnu++0x -fconst-strings -fdeprecated-macro -fdebug-compilation-dir /home/ubuntu/build/tor-browser/obj-macos/intl/icu/target/common -ferror-limit 19 -fmessage-length 0 -fvisibility hidden -pthread -stack-protector 1 -mstackrealign -fblocks -fobjc-runtime=macosx-10.6.0 -fobjc-dispatch-method=mixed -fobjc-default-synthesize-properties -fencode-extended-block-signature -fno-common -fdiagnostics-show-option -backend-option -vectorize-loops -o umutex.o -x c++ /home/ubuntu/build/tor-browser/intl/icu/source/common/umutex.cpp
1. /home/ubuntu/build/tor-browser/intl/icu/source/common/umutex.cpp:273:33: current parser token '{'
2. /home/ubuntu/build/tor-browser/intl/icu/source/common/umutex.cpp:250:1 <Spelling=/home/ubuntu/build/tor-browser/intl/icu/source/common/unicode/uversion.h:117:45>: parsing namespace 'icu_56'
3. /home/ubuntu/build/tor-browser/intl/icu/source/common/umutex.cpp:265:38: parsing function body 'umtx_initImplPreInit'
4. /home/ubuntu/build/tor-browser/intl/icu/source/common/umutex.cpp:265:38: in compound statement ('{}')
5. /home/ubuntu/build/tor-browser/intl/icu/source/common/umutex.cpp:272:12: in compound statement ('{}')
x86_64-apple-darwin10-clang: error: unable to execute command: Aborted
x86_64-apple-darwin10-clang: error: clang frontend command failed due to signal (use -v to see invocation)
clang version 3.3 (tags/RELEASE_33/final)
Target: x86_64-apple-darwin10
Thread model: posix
x86_64-apple-darwin10-clang: note: diagnostic msg: PLEASE submit a bug report to http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and associated run script.
x86_64-apple-darwin10-clang: note: diagnostic msg:
********************
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
x86_64-apple-darwin10-clang: note: diagnostic msg: /tmp/umutex-VR5zgw.cpp
x86_64-apple-darwin10-clang: note: diagnostic msg: /tmp/umutex-VR5zgw.sh
x86_64-apple-darwin10-clang: note: diagnostic msg:
********************
*** Failed compilation command follows: ----------------------------------------------------------
/home/ubuntu/build/x-tools/x86_64-apple-darwin10/bin/x86_64-apple-darwin10-clang++ -arch x86_64 -isysroot /home/ubuntu/build/MacOSX10.7.sdk -DU_ATTRIBUTE_DEPRECATED= -DU_COMMON_IMPLEMENTATION -DU_USING_ICU_NAMESPACE=0 -DU_NO_DEFAULT_INCLUDE_UTF_HEADERS=1 -DUCONFIG_NO_LEGACY_CONVERSION -DUCONFIG_NO_TRANSLITERATION -DUCONFIG_NO_REGULAR_EXPRESSIONS -DUCONFIG_NO_BREAK_ITERATION -DU_CHARSET_IS_UTF8 -I/home/ubuntu/build/tor-browser/intl/icu/source/common -I/home/ubuntu/build/tor-browser/intl/icu/source/i18n -Qunused-arguments -DU_HAVE_ATOMIC=0 -I/home/ubuntu/build/tor-browser/intl/icu/source/common -DDEFAULT_ICU_PLUGINS="/usr/local/lib/icu" -fPIC -Qunused-arguments -Wall -Wempty-body -Woverloaded-virtual -Wsign-compare -Wwrite-strings -Wno-invalid-offsetof -Wno-c++0x-extensions -Wno-extended-offsetof -Wno-unknown-warning-option -Wno-return-type-c-linkage -fno-exceptions -fno-strict-aliasing -frtti -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -DNO_X11 -pipe -UDEBUG -DNDEBUG -O3 -DU_STATIC_IMPLEMENTATION -fvisibility=hidden -fvisibility=hidden -fno-common -c -dynamic -MMD -MT umutex.d umutex.o umutex.o -o umutex.o /home/ubuntu/build/tor-browser/intl/icu/source/common/umutex.cpp
--- ( rebuild with "make VERBOSE=1 all" to show all parameters ) --------
make[7]: *** [umutex.o] Error 1
```
Trying to not compile ICU (using `--without-intl-api`) does not help. For some reason `umutex.ccp` still gets compiled.boklmboklm