Tor Browser 5.5.2 is released

Tor Browser 5.5.2 is now available from the Tor Browser Project page and also from our distribution directory.

This release features important security updates to Firefox.

Users on the security level "High" or "Medium-High" were not affected by the bugs in the Graphite font rendering library.

The full changelog since 5.5.1 is:

Tor Browser 5.5.2 -- February 12 2016

  • All Platforms
    • Update Firefox to 38.6.1esr
    • Update NoScript to 2.9.0.3
k239

February 15, 2016

Permalink

I can't use Full page. It try to make but not working. Win10 Enterprise 32bit.

k239

February 16, 2016

Permalink

I am the user of Tor Browser. It sometimes says that some other software is try to identify my computer. What should i do in this case. Will it be safe to go ahead or wait for the solution. Please advise.

Do you mean this notice?

Screenshot of the canvas warning.

Almost always, you can click "Not now" or "Never for this site". You only need to click "Allow in the future" for a few websites that require it.

The notice is Tor Browser's defense against canvas fingerprinting, which is a way to track web browsers by how they draw graphics. It is used a lot by web advertising companies.

Process: firefox [625]
Path: /Applications/TorBrowser.app/Contents/MacOS/firefox
Identifier: org.mozilla.tor browser
Version: 5.5.2 (3800.1.1)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: firefox [625]
User ID: 501

Date/Time: 2016-02-16 15:25:17.054 +0300
OS Version: Mac OS X 10.11.3 (15D21)
Report Version: 11
Anonymous UUID: 2C9A98D3-FE93-2258-3E15-896AF08E8552

Sleep/Wake UUID: 5CF91AA6-7602-434B-B8CA-915A87EAC831

Time Awake Since Boot: 5800 seconds
Time Since Wake: 2700 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 0x00000ab000000015
Exception Note: EXC_CORPSE_NOTIFY

VM Regions Near 0xab000000015:
mapped file 0000000125500000-000000012576a000 [ 2472K] rw-/rwx SM=COW
-->
STACK GUARD 0000700000000000-0000700000001000 [ 4K] ---/rwx SM=NUL stack guard for thread 1

Application Specific Information:
objc_msgSend() selector name: hash

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff95b7d4e9 objc_msgSend + 41
1 com.apple.Foundation 0x00007fff8ef2a4d8 -[NSConcreteMapTable objectForKey:] + 42
2 com.apple.UIFoundation 0x00007fff916a7809 +[__NSFontTypefaceInfo typefaceInfoForPostscriptName:options:] + 155
3 com.apple.UIFoundation 0x00007fff916ae56f __NSGetMetaFontInstance + 983
4 XUL 0x0000000102a7d425 0x1022d6000 + 8025125

Thread 1:
0 libsystem_kernel.dylib 0x00007fff980a36de __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff993af729 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff993ad365 start_wqthread + 13

Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff980a3ff6 kevent_qos + 10
1 libdispatch.dylib 0x00007fff99af8099 _dispatch_mgr_invoke + 216
2 libdispatch.dylib 0x00007fff99af7d01 _dispatch_mgr_thread + 52

Thread 3:
0 libsystem_kernel.dylib 0x00007fff980a36de __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff993af729 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff993ad365 start_wqthread + 13

Thread 4:
0 libsystem_kernel.dylib 0x00007fff980a36de __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff993af729 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff993ad365 start_wqthread + 13

Thread 5:: Gecko_IOThread
0 libsystem_kernel.dylib 0x00007fff980a3fc6 kevent + 10
1 XUL 0x0000000102540bd1 0x1022d6000 + 2534353

Thread 6:: Socket Thread
0 libsystem_kernel.dylib 0x00007fff980a3176 __select + 10
1 libnss3.dylib 0x00000001021ec565 poll + 485

Thread 7:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ff607 PR_WaitCondVar + 103

Thread 8:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ff607 PR_WaitCondVar + 103

Thread 9:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ff607 PR_WaitCondVar + 103

Thread 10:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ff607 PR_WaitCondVar + 103

Thread 11:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ff607 PR_WaitCondVar + 103

Thread 12:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ff607 PR_WaitCondVar + 103

Thread 13:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ff607 PR_WaitCondVar + 103

Thread 14:: Analysis Helper
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ff607 PR_WaitCondVar + 103

Thread 15:
0 libsystem_kernel.dylib 0x00007fff9809d386 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff9809c7c7 mach_msg + 55
2 XUL 0x0000000104462db0 0x1022d6000 + 35179952

Thread 16:: JS Watchdog
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767

Thread 17:: Hang Monitor
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ff607 PR_WaitCondVar + 103

Thread 18:
0 libsystem_kernel.dylib 0x00007fff980a36de __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff993af729 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff993ad365 start_wqthread + 13

Thread 19:
0 libsystem_kernel.dylib 0x00007fff980a36de __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff993af729 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff993ad365 start_wqthread + 13

Thread 20:: Timer
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ff699 PR_WaitCondVar + 249

Thread 21:: Cache2 I/O
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ff607 PR_WaitCondVar + 103

Thread 22:
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767

Thread 23:: Cert Verify
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ff607 PR_WaitCondVar + 103

Thread 24:: mozStorage #1
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767

Thread 25:: Proxy R~olution
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767

Thread 26:: SSL Cert #1
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ffd0f PR_Wait + 303

Thread 27:: RunProcess
0 libsystem_kernel.dylib 0x00007fff980a367e __wait4 + 10
1 XUL 0x00000001023621fe 0x1022d6000 + 573950

Thread 28:: IPDL Background
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767

Thread 29:: ImageIO
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767

Thread 30:: ImageDecoder #1
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ffd0f PR_Wait + 303

Thread 31:: Compositor
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 XUL 0x0000000102542aa8 0x1022d6000 + 2542248
3 ??? 0x8000000000000000 0 + 9223372036854775808

Thread 32:: ImageBridgeChild
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 XUL 0x0000000102542aa8 0x1022d6000 + 2542248
3 ??? 0x8000000000000000 0 + 9223372036854775808

Thread 33:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x00007fff9809d386 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff9809c7c7 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff8f6d7624 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff8f6d6aec __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff8f6d6338 CFRunLoopRunSpecific + 296
5 com.apple.AppKit 0x00007fff8c586065 _NSEventThread + 149
6 libsystem_pthread.dylib 0x00007fff993afc13 _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff993afb90 _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff993ad375 thread_start + 13

Thread 34:: DOM Worker
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ff607 PR_WaitCondVar + 103

Thread 35:
0 libsystem_kernel.dylib 0x00007fff9809d386 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff9809c7c7 mach_msg + 55
2 XUL 0x0000000104462295 0x1022d6000 + 35177109

Thread 36:: ImageDecoder #2
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ffd0f PR_Wait + 303

Thread 37:: ImageDecoder #3
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ffd0f PR_Wait + 303

Thread 38:: MediaManager
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767

Thread 39:: StreamTrans #11
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ffd0f PR_Wait + 303

Thread 40:: Cache I/O
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767

Thread 41:: mozStorage #2
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767

Thread 42:: mozStorage #3
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767

Thread 43:: localStorage DB
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ff607 PR_WaitCondVar + 103

Thread 44:: mozStorage #4
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767

Thread 45:: SSL Cert #2
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767
2 libnss3.dylib 0x00000001021ffd0f PR_Wait + 303

Thread 46:: URL Classifier
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767

Thread 47:: HTML5 Parser
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767

Thread 48:: mozStorage #5
0 libsystem_kernel.dylib 0x00007fff980a2eb2 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff993b0150 _pthread_cond_wait + 767

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000008 rbx: 0x000000010079a9a0 rcx: 0x0000000000000000 rdx: 0x00007fff5fbf4d80
rdi: 0x000000010079a9a0 rsi: 0x00007fff8fac806a rbp: 0x00007fff5fbf4d70 rsp: 0x00007fff5fbf4d28
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x00000ab000000015 r11: 0x0000000100000000
r12: 0x29004e90cd1b0173 r13: 0x000000010079a9a0 r14: 0x00007fff78a3e0b8 r15: 0x000000010bac4c70
rip: 0x00007fff95b7d4e9 rfl: 0x0000000000010202 cr2: 0x00000001160980ac

Logical CPU: 0
Error Code: 0x02000131
Trap Number: 133

EDIT (gk): Thanks the above should be enough for trying to track you issue down.

[snip]

Thanks. Is that reproducible? If so, how?

I've been unable to use obfs4 custom bridges since 5.5 and it still doesn't work. I used custom bridges when obfs3 was the default and used obfs3 custom but now with obfs4 it doesn't work anymore,I can't use obfs4 custom. Don't know why. I haven't change anything else in tor browser.

[WARN] Proxy Client: unable to connect to xxx.xxx.xxx.xx:xxxxxx ("general SOCKS server failure")

[WARN] Proxy Client: unable to connect to xxx.xxx.xxx.xx:xxxxxx ("general SOCKS server failure")

Your bridges might be down? I just tested it in a Tor Browser 5.5.2 on Linux with a custom obfs4 bridge and it works fine for me.

I've see this same bug with bridges that I know to be up and working. There's a Trac ticket on this.

I've received 7 obfs4 unlisted relays by BridgeDB in the last 2 months. Two of the relays always work, the other 5 never work.

ok

Wow! Interesting update.

Such a minor update...

deepweb?

*Important* question:
Is TAILS vulnerable?:

Remote Code Execution. DNS-Code (getaddrinfo)! glibc!
http://arstechnica.com/security/2016/02/extremely-severe-bug-leaves-diz…
https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html

glibc is patched on debian & ubuntu (slackware is not vulnerable) _ tail is vulnerable as o.s until the next release but , like it is a cd live , i think you can use it.

All speculation here, but I think stack smashing protection (SSP, a feature of GCC) would prevent the remote code execution vuln though not the denial of service. I cant imagine Tails is built without SSP.

thanks :D

thanks for your work

OK

It is creepy that a web server can log what text a users selects on a page for copying.
Tor Browser mitigates this with anonymity but I think dom.event.clipboardevents.enabled should be set to false by default.

Bangla font did not shown.

Danke!!!

Do not operate ONION sites. Upload, but give the error "Unable to Connect". Version - 5.5.2.

thanks so much

Most appreciable browser is this "TOR"

Хоть кто-то проделывает эту работу! Оромное спасибо! (сделаю внос как-только опредеделюсь,как...)

Thanks

Good

Мне нравится )

Thanks for the updates. Your hard work is much appreciated.

nice one

Thank you

OpenSSL 1.0.2g and 1.0.1s security releases due 1st Mar 2016

I've looked at the release notes for the new version, and it looks like Tor should be ok. (It will still be a good idea to upgrade, for your other applications, maybe.)

I know you're not supposed to add any addons... but what would be the risk of just using Tor + ublock origin?

cheers.

hello torproject,
The TAILS distributors will replace Vidalia in TAILS 2.2. Good, its unmaintained for years.
https://tails.boum.org/news/test_2.2-rc1/index.en.html

https://labs.riseup.net/code/issues/6841
BUT, there seems to be no substitute for
Settings -> Advanced -> 'Edit current torcc'.
With editing torcc you can set custom Guard Nodes.
Necessary/mandatory when you boot Tails with DVD.
Otherwise, you won't have normal Guard security like TBB.
This would be a big problem! Wouldn't ?

Without editing torcc for Guard Nodes, TAILS would be a REALLY big problem here)-:.
Please Help. It's important.

Thank a lot tor developers... Great upgrade..good job..

Icant save my passwords...help me plz

Recently I'm upgrade to Tor bundle 5.5.2 I want to write on my wordpress.com and wix.com websites using it As I see it It doesn't work at all. Even I can't post any single thing. While I use firefox+blackbeltprivacy or manually connect my firefox to torbundle by using socks 127.0.0.1 and port the tor port, it works. Now is it Firefox of Tor in question or is it tor routers who in glitch?

Bangla Font is not shown. Please provide solution.

[edit] leaving personal information out, gk

Could you give us an example URL that is broken for you?

Facebook no longer works in this new version. Can anyone attempt it?
I am using the .onion rather than .com URL.
Able to login but unable to view any pictures.

Can anyone answer me why in this update i cannot open .onion sites
and they all open with .cab from the proxy tor2web?I cannot access any hidden services and cant seem to configure it to use Tor directly without the proxy .cab? I remember this happening about 2 years ago with a previous update what are the solutions?

I can't find the shockwave plugg in is there any alternative add on?

I have seen that some videoes are not playing in my browser. it shows that " a plug in is required". how to download a plugin which plays video????