Tor Browser 7.0.10 is released
Tor Browser 7.0.10 is now available from the Tor Browser Project page and also from our distribution directory.
This release features important security updates to Firefox.
This release updates Firefox to version 52.5.0esr and Tor to version version 0.3.1.8, the second stable release in the 0.3.1 series. In addition to that we updated the HTTPS Everywhere and NoScript extensions we ship. For Windows users we backported patches from the alpha series that update the msvcr100.dll runtime library we include and which should make Tor Browser more robust against crashes due to misbehvaing third party software.
The full changelog since Tor Browser 7.0.9 (7.0.8 for Windows) is:
- All Platforms
- Update Firefox to 52.5.0esr
- Update Tor to 0.3.1.8
- Update Torbutton to 1.9.7.10
- Bug 23997: Add link to Tor Browser manual for de, nl, tr, vi
- Translations update
- Update HTTPS-Everywhere to 2017.10.30
- Bug 24178: Use make.sh for building HTTPS-Everywhere
- Update NoScript to 5.1.5
- Bug 23968: NoScript icon jumps to the right after update
- Windows
Comments
Please note that the comment area below has been archived.
NoScript is still on the…
NoScript is still on the right after this update. Should I be worried that I have a different fingerprint than the others? I'm on Trisquel x86 BTW...
I would like to add No…
I would like to add No Script is also still on the right on my screen, if that makes any difference. Also again, many thank yous to all who work so hard on Tor.
Was it already on the right…
Was it already on the right before the update? You can click on the hamburger menu on the top-right and select 'Customize' to move it back to the left.
The bug which moved it to the right on an update should be fixed:
https://trac.torproject.org/projects/tor/ticket/23968
However I don't think this should affect the fingerprint.
Yes, It was already there…
Yes, It was already there before the update. I installed a new one and NoScript still moved to the right after relaunching (Ctrl+Shift+U) it today. However I got a "yes" result in "Does your browser protect from fingerprinting?" after testing it with EFF's Panopticlick, so I guess it should be fine.
Не волнуйся-какая разница в…
Не волнуйся-какая разница в каком углу-работает ? Вот и хорошо !
Very Thanks to all who work…
Very Thanks to all who work on This Tor this Program is for Save the Internet and Keep The World Clean from Hacking and Profit
My best Regards on you
New u
New user and want to donate . this network fills secure .Which is the best way?
You can see the possible…
You can see the possible ways to donate on https://qmcgghbwqt.oedi.net/.
please update…
please update
Bug 23997: Add link to Tor Browser manual for kw, om
I don't understand your…
I don't understand your comment. Bug 23997 did not add links for kw, om. And I don't see them on https://tb-manual.torproject.org/.
Usefull.Difficult to browse
Usefull.Difficult to browse
Beautiful work devs! …
Beautiful work devs!
Pretty please can we get level 3 content sandboxing in FF 57 patched to work with Linux Tor Browser? :-)
January 23rd the Firefox 59…
January 23rd the Firefox 59 beta drops, which will be the basis for ESR 59 in March. Mark your calendar as it ought to be the best time to prepare for the first TBB based on this ESR.
No matter how you update we…
No matter how you update we are satisfied!
Too good finally solved the…
Too good finally solved the crash problem
09:15:43.600 DOMException …
09:15:43.600 DOMException [InvalidStateError: "A mutation operation was attempted on a database that did not allow mutations."
code: 11
nsresult: 0x80660006
location: resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/async-storage.js:80] 1 Promise-backend.js:935
lot of Updates! on and on…
lot of Updates! on and on and on! when reaches to its end? Terrorists and suicide bombers, mass shooters etc, doing freely, but internet users are not free! why internet users are under intense surveillance, but Terrorists acting freely?
How one could be sure about theses ridiculous Zeros and Ones which come and get out of PC's, not to be seen by third parties, adversaries, terrorist regimes installed by U.S.A,?
just some ridiculous Green lock or some jumping relays, could prevent third parties watch our communications?
who don't know that every signal on all over the planet Earth are traceable, view-able and decodable, by surveillance centers? just an easy Dos command like "netstat/n" can show you after running the Tor browser, other creepy connections get you in touch and exploit your data stream!
watch out Tor users, there's no lock in all the world that could not have got a correct key.
you are misinformed :…
you are misinformed :
- internet users will be free when isp & free-lance actors (often illegally) will pay their activities done against the users : the contract between a client and a service is not at all in favor of the client (the users) ; it is a commercial matter not a politic one.
- a terrorist regime is a rogue-state like france e.g , in a true democracy/republic it can't happen & usa does not install it (imo).
- most of signals are encrypted and not traceable , it is not because you 'see' that you 'know' (imo).
The danger is not (in my own opinion) about Tor or Tor network.
It should be far better if encryption was legalized as a fundamental right and if our lives were respected as our own propriety : it is a matter of force/will of a whole people/region not a police one.
I am now more happy than…
I am now more happy than yesterday :-)
i strongly disagree with…
i strongly disagree with your self-satisfaction :
- security.enable_tls
- network.IDN_show_punycode
- security.ssl3
and why do you not implement a Calomel-add-on version (it does not connect at the network_passive addon : privacy respected) ?
i need a secure Tor Browser not a windows_cop_toy !
This has been answered in…
This has been answered in this ticket:
https://trac.torproject.org/projects/tor/ticket/24239
Tor is not a secure browser…
Tor is not a secure browser but a government/google compliant.
This has been answered in this ticket : firefox is poorly secured ...
The Users need a secure browser not a jc jones for guru.
This has been written in this ticket: https://trac.torproject.org/projects/tor/ticket/24239
Every one does now know that clearly , Tor & firefox & https (gmail&google !!!) are not on the line they claim ; they are running like an electric car , just following the same rules, the same roads, it sounds like anonymous means in your mind/brain 'without identity/personality walking slowly blind & deaf until the retreat : the maffia blues.
If you have built just a foss version of internet explorer (microsoft innovation = google = Tor Browser) it is a big misunderstood !
The users of the net do not need & want that & you still wonder why so few people are using Tor ?
my firefox is less anonymous and i can't access to the onions but it is more secure and Onions are useless if it is an open door and it is a big & large window that you open without securing better Tor.
Tor is not built privacy & security in mind : it is a false assertion, a lie ; it is just a microsoft joint-venture with free software foundation : hypocrite.
Could you add a bit more…
Could you add a bit more substance to your rambling? Why does Tor Browser not have privacy built in mind? We have a lengthy design document we follow which is addressing exactly that issue: https://decvnxytmk.oedi.net/projects/torbrowser/design/.
The time has changed !…
The time has changed !
Your 'template' https://decvnxytmk.oedi.net/projects/torbrowser/design/ (design document written for the version 6.1) is your project but we need something else & better now.
Before it was a new idea re-appropriating a free space , now we want move together with trust in mind , and tomorrow it will be different.
I suppose you hide the users behind 30 millions of civil servant (gov compliant etc.) & behind a professional-commercial flux (google_microsoft_gmail etc.) but you provide a link which said "des is secure (& rc4 too !)" because it is a govt demand ... so your idea of legality means a deal like a secret shared between a state and a personal opinion : both are the same person involved in an imaginary and a very small world : a retarded dream without autonomy (who was the ideal/model user ?).
I admit that your client are your sponsors and follow the u.s request but in this case, it is for them only : a reserved-private tool which the term 'privacy' implies your own concept & their will.
It is not exportable and not an universal translation of a genuine right.
So your presentation [The Tor Project is a US 501 non-profit dedicated to the research, development, and education of online anonymity and privacy & You are now free to browse the Internet anonymously] is an intellectual lie , a dishonest assertion in every word & comma.
I should add that you act with bad faith : you are not behind mozilla you are in front of it as soon as you run tor.
You cannot offer better than mozilla if you do not first built yours then add your tor config : you did not , you take it as a source without accepting the idea to first harden yours and you are wrong : the sites - even the most obscure, old, reticent - must update their configuration to enter in the xxi century or must be avoided (https is one example, cypher is another one ...). I, i should not be confidence in my army; police force or another public service -elective dpt e.g- and unknown friends or enemies if the contact (surfing is one example, emailing is another one...) was not secure and anonymous.
It is not an angry, geek, absurd, paranoid feeling. It is just a minimum to be safe ; a secure Tor Browser not a cop_toy.
It is obvious, clear and sane : Tor Browser is not built privacy/security in mind ... just a cheat code, a proof of concept for the fun ... and does not provide the anonymity level that they claim.
The critic make sense in a…
The critic make sense in a general way on the attitude of mozilla.
They (mozilla) are marketing a privacy imago while they do not really make a real effort to work on it.
They publish reports on privacy, they support Tor and Tails which is all nice but these are big company tactics of walking to different roads. The marketing road for public association for the brand and the quite separate road for their own products.
Why deliver a browser with privacy options that are deactivated when you install it?
They know most users are installing products and go along without making a study of all the settings.
Why making the preferences panel 'easier' but actually hiding options so people have to work on a complete lost of about config settings to make this browser shut up and work?
But the best illustration is on their mobile products.
Now tell me, if you really are a privacy minded company, why the X are you releasing two versions of your mobile browser, a non privacy minded browser and a 'special' browser that has privacy options?
Why were they keeping up the system requirements higher (smaller market segment) for the privacy minded browser?
Why is there a huge difference between onion browser system requirements (systems req. lower is a broader market is better for more users) and the so called special privacy browser from firefox?
The standard browser on mobile is already for years a total anti privacy minded browser.
The desktop browser version of mozilla is for years a total pain in the privacy head because after every release on has to make a study of what they secretly changed, removed, added that might affect your privacy and make you work on the about:config again.
This is not a problem for users but also for developers, big privacy bugs in Torbrowser because at mozilla side they added something fancy again.
So, yes, in a way that poster has a point on attitude which is also illustrated here.
https://bugzilla.mozilla.org/show_bug.cgi?id=1408647
Question to Torproject, are you going to follow Mozilla ignoring policies or really protect your Torbrowser users by reconsidering the Certificate Authority section.
You should because it is better to be safe that sorry afterwards and it is total madness to ignore loud signals of reality. Especially when you do not have to search for them but getting them as feedback.
Nobody asks you to bite in the hand that is feeding you.
But since Torbrowser is already a modification of the mozilla browser it should not be a problem to defend your users for the ignoring policies and mistakes your feeder is making.
Be convincing in your decisions when people are concerned and act to it because, many countries are trying to control the internet by themselves or by cooperating together.
Therefore it should be better that the Tornetwork is not only hosted in the western 5-19 eyes world and you really should look over and over again to what you trust in your browser.
To me that is the implicit message in the posting of the other person writing.
I think I must have a…
I think I must have a counterfeit download... my "HTTPS Everywhere" extension says it is from "eff.software.projects@gmail.com" which is obviously not legit (if it was really from EFF I'm sure they would use an eff.org email address). Please advise.
This is the real HTTPS…
This is the real HTTPS-Everywhere extension. This is the email they chose to use as the author:
https://gitweb.torproject.org/https-everywhere.git/tree/chromium/manife…
https://github.com/EFForg/https-everywhere/blob/master/chromium/manifes…
And just to clarify further:…
And just to clarify further: the EFF is using a Gmail simply because that's required for putting the extension in the Google Chrome Addon Store.
Is this ok or suspect? …
Is this ok or suspect?
15/11/2017 12:40:22.100 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
15/11/2017 12:40:22.100 [NOTICE] Opening Socks listener on 127.0.0.1:9150
15/11/2017 12:40:23.000 [NOTICE] Bootstrapped 80%: Connecting to the Tor network
15/11/2017 12:40:23.800 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop
15/11/2017 12:40:23.800 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
15/11/2017 12:40:24.400 [NOTICE] Bootstrapped 90%: Establishing a Tor circuit
15/11/2017 12:40:24.500 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
15/11/2017 12:40:24.500 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
15/11/2017 12:40:24.600 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
15/11/2017 12:40:24.600 [NOTICE] new bridge descriptor 'griinchux' (fresh): $011F2599C0E9B27EE74B353155E244813763C3E5~griinchux at 85.31.186.98
15/11/2017 12:40:24.600 [NOTICE] new bridge descriptor 'zipfelmuetze' (fresh): $91A6354697E6B02A386312F68D82CF86824D3606~zipfelmuetze at 85.31.186.26
15/11/2017 12:40:24.700 [NOTICE] Bridge 'NX01' has both an IPv4 and an IPv6 address. Will prefer using its IPv4 address (85.17.30.79:443) based on the configured Bridge address.
15/11/2017 12:40:24.700 [NOTICE] new bridge descriptor 'NX01' (fresh): $FC259A04A328A07FED1413E9FC6526530D9FD87A~NX01 at 85.17.30.79
15/11/2017 12:40:24.800 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
15/11/2017 12:40:25.000 [NOTICE] new bridge descriptor 'cymrubridge31' (fresh): $C8CBDB2464FC9804A69531437BCF2BE31FDD2EE4~cymrubridge31 at 38.229.1.78
15/11/2017 12:40:25.100 [NOTICE] new bridge descriptor 'ndnop5' (fresh): $BBB28DF0F201E706BE564EFE690FE9577DD8386D~ndnop5 at 109.105.109.147
15/11/2017 12:40:25.100 [NOTICE] new bridge descriptor 'LeifEricson' (fresh): $A09D536DD1752D542E1FBB3C9CE4449D51298239~LeifEricson at 83.212.101.3
15/11/2017 12:40:25.200 [NOTICE] new bridge descriptor 'ndnop3' (fresh): $8DFCD8FB3285E855F5A55EDDA35696C743ABFC4E~ndnop3 at 109.105.109.165
15/11/2017 12:40:25.300 [NOTICE] Tor has successfully opened a circuit. Looks like client functionality is working.
15/11/2017 12:40:25.300 [NOTICE] Bootstrapped 100%: Done
15/11/2017 12:40:25.300 [NOTICE] new bridge descriptor 'cymrubridge33' (fresh): $0BAC39417268B96B9F514E7F63FA6FBA1A788955~cymrubridge33 at 38.229.33.83
15/11/2017 12:40:26.000 [NOTICE] new bridge descriptor 'frosty' (fresh): $88CD36D45A35271963EF82E511C8827A24730913~frosty at 37.218.240.34
15/11/2017 12:40:26.300 [NOTICE] new bridge descriptor 'dragon' (fresh): $D9A82D2F9C2F65A18407B1D2B764F130847F8B5D~dragon at 37.218.245.14
15/11/2017 12:40:26.500 [NOTICE] New control connection opened from 127.0.0.1.
15/11/2017 12:40:26.600 [NOTICE] New control connection opened from 127.0.0.1.
15/11/2017 12:42:31.100 [WARN] Proxy Client: unable to connect to 154.35.22.12:4304 ("general SOCKS server failure")
15/11/2017 12:42:31.100 [WARN] Proxy Client: unable to connect to 192.99.11.54:443 ("general SOCKS server failure")
15/11/2017 12:42:31.100 [WARN] Proxy Client: unable to connect to 154.35.22.9:80 ("general SOCKS server failure")
15/11/2017 12:42:31.100 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
15/11/2017 12:42:31.100 [WARN] Proxy Client: unable to connect to 154.35.22.11:80 ("general SOCKS server failure")
It seems like someone is…
It seems like someone is blocking the connections to bridges we ship with Tor Browser. Have you tried getting bridge addresses that are not as exposed, for instance by querying https://bridges.torproject.org ?
Thank you…
Thank you.
Do you change basic bridges shipped on every version of Tor Browser?
I have made a new and fresh install of Tor Browser Bundle, problem seams to be solved.
We sometime add or remove…
We sometime add or remove default bridges, but not on every version of Tor Browser.
Подскажите пожалуйста, у…
Подскажите пожалуйста, у меня TOR подключается к remote address johndeere.ratwerks.com по imaps
Так должно быть или нет?
Скорее всего это один из…
Скорее всего это один из EntryGuard - вход в сеть Tor.
Вход по HTTPS и он…
Вход по HTTPS и он отображается в соединениях. А это соединение IMAPS. Два одновременно работают.
https://atlas.torproject.org…
https://atlas.torproject.org/#details/AD1B3496B2CE5352A1D69E1D1CB7EC1BA…
Рекомендую почитать немного доков, как устроена Tor-сеть :-)
Извините я не специалист в…
Извините я не специалист в этом и мне трудно разобраться в документации на английском языке, но насколько я понял TOR одновременно работает только с одним входным узлом и все соединения которые он открывает, направляются через него (так показывает программа Tcpview).
А здесь получается одновременно два удаленных узла с которыми работает TOR и один из них johndeere.ratwerks.com передача на который идёт по почтовому протоколу imap (143 порт).
Я всего лишь хотел получить простой ответ.
Простой ответ по ссылке…
Простой ответ по ссылке. Узел является входной точкой Tor. Все в порядке.
Порт может быть любым, хоть http. Соединений может быть несколько, они могут открываться, закрываться, ждать и т.д. Если не специалист, зачем смотреть соединения, которые для специалистов? :-) Все у вас ок с этим соединением, не переживайте.
Спасибо. :-)
Спасибо. :-)
changelog mentions 24052 for…
changelog mentions 24052 for windows, is that a typo or is the workaround now applied to windows as well
Version 7.0.9 which added…
Version 7.0.9 which added the patch for #24052 was released for Linux and macOS only. In 7.0.10 this patch is applied to the Windows version as well.
FANTASTIC! Just what I was…
FANTASTIC! Just what I was hoping for. For a couple weeks there I thought Windows would have some implied superiority complex over a bug in e10s until ESR 59. Phew. It also makes it clear TPO doesn't endorse the usage.
Another question: Does TBB rely entirely on sandboxing functionality provided by Mozilla? Meaning level 3 happens with ESTR 59?
For the sandboxing, we have…
For the sandboxing, we have started with backporting some patches from Firefox 54:
https://trac.torproject.org/projects/tor/ticket/22692
mmHmm, I saw that. So then…
mmHmm, I saw that. So then since level 3 is part of "NEXT" that would suggest what is needed is a somewhat stable NEXT like v59b in January (basis of ESR NEXT). That, or redo some work in the 2mo in-between, just to prolong the life expectancy of ESR 52 based TBB...until at most Julyish. +1 for as soon a transition as possible!
Thanks for the update!…
Thanks for the update!
Any plans or timeline for FF Quantum as Tor Browser?
Tor Browser will switch to…
Tor Browser will switch to the new ESR branch with Firefox 59.2 which is planned for 2018-07-03:
https://wiki.mozilla.org/RapidRelease/Calendar
Thanks. Good idea not to…
Thanks. Good idea not to hurry with the new browser so many bugs can fixed till July 2018
Is there a plan for an alpha…
Is there a plan for an alpha in advance? Anything code wise that can be done to assist in preparation?
There is at least one alpha…
There is at least one alpha before we switch to a new ESR, usually two to test fixups before they reach release. We have the
ff59-esrkeyword to track tickets we deem important for the next switch: https://trac.torproject.org/projects/tor/query?status=accepted&status=a… feel free to pick any of them not assigned to someone in particular and start working on them. That's really appreciated or just ask on the tbb-dev mailing list or on #tor-dev on the OFTC IRC network if unsure. Thanks.With the last update to 7.0…
With the last update to 7.0.10, *all* the files in my TBB folder, even in /tor-browser/Browser/Downloads, have an identical timestamp (the one of the update on my machine, I guess). Is that expected behaviour (which would be not so good), or a bug (which would be not good at all), or something that indicates my machine was compromised in some way (which would be less bad for everyone, yet much worse for myself)?
Appreciate any reply, I am really worried here.
That's due to our…
That's due to our deterministic build system, see: https://trac.torproject.org/projects/tor/ticket/11506. I would not call it a bug but I agree we could do better here so that it is less confusing for users.
1. Damn gvfsd-metadata bug…
1. Damn gvfsd-metadata bug every version
2. Tor circuit for this site: Bridge (Germany) - Relay (Germany) - Exit (Germany)-Internet
Tor project is a part of a CIA :)
What is the gvfsd-metadata…
What is the gvfsd-metadata bug?
Tor will avoid using more than one router in the same /16 subnet in a circuit, however they can be in the same country.
What better way to isolate a…
What better way to isolate a group of peo to monitor than to tell them it's all clear here.;-D Where's your faith.
Anyone else found that…
Anyone else found that upgrading from TBB 7.0.7 to TBB 7.0.10 breaks embedded webextensions?
I'm aware that Mozilla are dropping support for embedded webextensions in FF57, but TBB 7.0.10 is meant to be based on FF 52.5.0 - did Mozilla do something weird between 52.4.1 and 52.5.0?
Could you give us some steps…
Could you give us some steps to reproduce your problem?
https://bugzilla.mozilla.org…
https://bugzilla.mozilla.org/show_bug.cgi?id=1136836
Here you go, I've made a…
Here you go, I've made a basic test case for you:
https://trac.torproject.org/projects/tor/ticket/24504
No idea what is causing it though. Turns out it isn't something Mozilla have done, because it works fine in vanilla FF.
PS I can't see any obvious way in which it relates to the mozilla bug another commenter posted.
Installing the new Version 7…
Installing the new Version 7.0.10 on Windows 10 actual Version I get the error message:
"Tor Browser does not have permission to access the profile. Please adjust your file system permissions and try again."
What can I do?
I am not exactly sure what…
I am not exactly sure what happened. Maybe you installed Tor Browser as an administrator and now try to start it as a "normal" user?
Had the same type of message…
Had the same type of message about ccleaner portable from windows defender after installing the Fall Creators update
ublock origin doesn't filer…
ublock origin doesn't filer ads anymore right? the button formerly displayed in the toolbar has disappeared too.
Tor and the tor devs RULE! …
Tor and the tor devs RULE! Great work by them as always -- and as always I am immensely grateful.
With Javascript off, HTTPS…
With Javascript off, HTTPS-Everywhere in TBB7.0.10 is working normal?
During my work with buggy HS…
During my work with buggy HS I noticed this:
XX:21:37.000 [notice] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
XX:26:59.000 [notice] Short path bias probe response length field (1).
XX:30:54.000 [notice] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
I suspect it is some bug (message "Short path bias probe response length field"). Time of this message corresponds to a moment when HS stopped working. I have no idea about its relation to old ticket #8962.
Is it dangerous message? Is it sign of attack against tor client?
As always it was, with this…
As always it was, with this version it is also:
./start-tor-browser: line 368: 1651 Segmentation fault TOR_CONTROL_PASSWD=${TOR_CONTROL_PASSWD} ./firefox --class "Tor Browser" -profile TorBrowser/Data/Browser/profile.default "${@}" < /dev/null
JS is disabled, security slider is "high". I don't know how to reproduce.
Would you be willing to run…
Would you be willing to run a debugger,
gdbif we explained to you how to do so? But more importantly which Linux distribution are you using?Debian jessie, 64 bit, TBB…
Debian jessie, 64 bit, TBB in VM, tor is on host OS, no pulseaudio. Slider was at high. I think it is safe to debug with gdb, because my VM doesn't have access to tor guards, etc. So, the leak is only my exit node or particular HS used at that time, I could tolerate that. Actually, TBB with JS enabled crashes even more often.
Please, explain me how to use gdb. Ideally I would like to run just another version of tor browser which writes detailed log useful for you. Do I need to enable core dumps somewhere in sysctl?
The situation with the tor itself is much worse, because it is impossible to debug without disclosing too much about my IP, guard, and my tor chains. Maybe tor project needs to think how to address this problem (creation of safe tor debug log).
You should get a stack trace…
You should get a stack trace by following the instructions on https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/Hacking#Us… (adapt the version number of the symbol URL to the one you are using).
Thanks! I followed…
Thanks! I followed the instructions on link you gave me. So, as I understand, after downloading, unzipping, etc., in my starting script I need to do this:
$ ulimit -c unlimited
$ cd $HOME/tor-browser_en-US
$ gdb -x commands ./Browser/firefox ./Browser/core
where
commandsis a file with the content:set env LD_LIBRARY_PATH=Browser/TorBrowser/Tor
run -profile Browser/TorBrowser/Data/Browser/profile.default
quit
Then, if torbrowser crashes, I need to give you just a (compressed) file
core, that's all? I checked it, and indeed, it seems working this way.However, fonts in address line and in interface elements in torbrowser now look different. I guess it is because torbrowser is not started through start-tor-browser script, i.e. some libraries may not be loaded. So, do I have risk to be profiled when running TBB in gdb?
Also, I don't understand why I see this complaint:
/home/user/tor-browser_en-US/./Browser/core: No such file or directory.
Is something wrong with the command "gdb -x commands ./Browser/firefox ./Browser/core"? If I kill torbrowser with -9, core file is created in directory tor-browser_en-US, and not in tor-browser_en-US/Browser as specified by command.
By the way, (I don't know if it is normal or not) if I do just this, it gives error:
$ ./Browser/firefox
./Browser/firefox: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by ./Browser/firefox)
Finally, I don't know if it matters or not, but I have only dbus libraries installed and not dbus itself (usually I have no problems with this setup). My /etc/machine-id file is empty. So, I see some complaints about it at each TBB startup, but everything works. I don't think that crashes are related to these things.
In addition to my previous…
In addition to my previous comment:
Indeed, fonts are not the same, because
start-tor-browserscript exports few fonts-related variables. Now I have tried to be as close to this script as possible when running my torbrowser ingdb. Finally, I arrived at this way:Start torbrowser using script:
-----
#!/bin/sh
ulimit -c unlimited
cd $HOME/tor-browser_en-US
if [ ! -d ".config/ibus" ]; then
mkdir -p .config/ibus
ln -nsf ~/.config/ibus/bus .config/ibus
fi
gdb -x $HOME/bin/commands.1 ./Browser/firefox ./Browser/core
-----
Here file
commands.1is:set env XAUTHORITY=/home/username/.Xauthority
set env HOME=/home/username/tor-browser_en-US
set env LD_LIBRARY_PATH=Browser/TorBrowser/Tor
set env FONTCONFIG_PATH=Browser/TorBrowser/Data/fontconfig
set env FONTCONFIG_FILE=fonts.conf
run -profile Browser/TorBrowser/Data/Browser/profile.default
quit
Now fonts look normal as with usual TBB, and no extra files are created in home dir (like ~/Desktop). Is it correct configuration to start using my "gdb-version" TBB as usual browser? Do I still have any profiling risks?
P.S. I'm sorry for being…
P.S. I'm sorry for being messed with paths... Well, the correct version I mean is:
1) Script to start browser:
#!/bin/sh
ulimit -c unlimited
cd $HOME/tor-browser_en-US/Browser
if [ ! -d ".config/ibus" ]; then
mkdir -p .config/ibus
ln -nsf ~/.config/ibus/bus .config/ibus
fi
gdb -x $HOME/bin/commands ./firefox ./core
2) $HOME/bin/commands file:
set env XAUTHORITY=/home/username/.Xauthority
set env HOME=/home/username/tor-browser_en-US/Browser
set env LD_LIBRARY_PATH=TorBrowser/Tor
set env FONTCONFIG_PATH=TorBrowser/Data/fontconfig
set env FONTCONFIG_FILE=fonts.conf
run -profile TorBrowser/Data/Browser/profile.default
quit
If you want to debug your…
If you want to debug your crash there is not need to mess with any start scripts or write your own.
1) Just download the debug symbols (the large .zip file) and make sure everything lands properly in
Browser/.debug2) Follow the "Starting firefox from inside gdb" instructions
Reading your above comments it seems this is kind of working for you? If so, you might want to play with the
Browser/start-tor-browserscript figuring out what exactly it is that breaks your setup.If you want to debug your…
Well, I was a bit confused. I thought that I need to specify some core file during start of program to get it created during a crash. Actually, it is not so, as I understood it later... So, normally I should start
gdbon firefox without any core file, as it will be automatically created if crash happens. Then, if crash has happened with some core file created, I can run firefox on this core file and investigate it (creating stack trance, etc.). I hope, now I am correct. :)Yes, everything works. I downloaded, unzipped, all right. Core file is created if firefox is killed. But I want this working smoothly as an everyday usage of torbrowser, that's why I need to care about all variables, correct fonts, and absence of profiling (because of some possible misconfiguration).
It is not breaking. Everything works. At least, I cannot see any visual differences with normal TBB (i.e. without
gdb). Yes, it doesn't mean there are no such differences.Initially I thought that
gdbdoesn't take environment variables from my shell before running the program, that's why I tried to pass all necessary variables to firefox after gdb is launched. Now I see this is wrong. So,gdbcan safely get all necessary variables from shell, i.e. I simply need just to edit that lines ofstart-tor-browserscript, where firefox is launched, by replacing them with a propergdbcommand.To be clear: Since most of crashes are not easily reproducible, my intention is to use
gdbwith torbrowser by default. Then, if crash happens in some future, I will come here with useful backtrace and a core file. I hope it will make TBB more secure and will help the community to catch yet unknown torbrowser 0-days.Okay, so without gdb Tor…
Okay, so without
gdbTor Browser is working as well? If so, good. And thanks for helping to find bugs in Tor Browser. Really appreciated.Thank you for the help! Yes,…
Thank you for the help! Yes, my TBB now can work both with and without
gdb. Crashes usually happen rarely (I don't think that more than once in a week), but I almost sure that once I'll get them in my future. It should be interesting to analyze... (Well, it may be also due to other possible reasons: bug in other Linux libraries or kernel, hardware bugs, etc.).Finally, the hack with these…
Finally, the hack with these extra 6 lines is working:
-----
$ diff start-tor-browser.new start-tor-browser.original
116,119d115
< --gdb)
< use_gdb=1
< shift
< ;;
367,369d362
< [[ "$use_gdb" -eq 1 ]] && TOR_CONTROL_PASSWD=${TOR_CONTROL_PASSWD} gdb \
< -ex "run --class 'Tor Browser' -profile TorBrowser/Data/Browser/profile.default ${@} < /dev/null" \
< -ex quit ./firefox ||
-----
I added one switch
--gdb, so now one can use both ways. Withoutgdb:$ ./start-tor-browser -v
With
gdb:$ ./start-tor-browser -v --gdb
If you like it, you could add some similar functionality to
start-tor-browserscript (at the moment I don't care about regimes and options other than-v, but it can be easily applied to all places in the script, where firefox is launched).Finally, the hack with these…
P.S. In addition, though
ulimitis unlimited by default, one still needs to add the lineulimit -c unlimitedsomewhere at the start of
start-tor-browserscript. Otherwise,corefile will not be created.tor browser can be…
tor browser can be resuscitated in china, if we use a socks-5 proxy server as vanguard.
Is it safe to use Vidalia(…
Is it safe to use Vidalia(.exe)? I find it indispensable for viewing and playing with Tor circuits.
Should the control port in Vidalia be 9150 or 9151? Thanks.
The default control port is…
The default control port is 9151.
For Vidalia, it has been unmaintained for a few years.
TB opens up as maximized on…
TB opens up as maximized on Debian 9
And without https Everywhere "S"
But after a restart S appears normal
Is this after an update? Are…
Is this after an update? Are you able to reproduce the problem if you reinstall the previous version and update it again?
No I downloaded the complete…
No I downloaded the complete TB and when it starts it is maximized and without the S. After a restart the S seems Ok, but again TB is maximized. This has been this way in several recent versions of TB.
What window manager are you…
What window manager are you using and what screen resolution are you getting when testing it on e.g. https://browserleaks.com/javascript?
Screen resolution: 915×539…
Screen resolution: 915×539 24-bit TrueColor (working area: 902×539)
x window manager alias mutter
All from debian live 9 stretch on an old toshiba satellite
I see. I've opened https:/…
I see. I've opened https://trac.torproject.org/projects/tor/ticket/24383 for further investigation, thanks.
Which window manager are you…
Which window manager are you using? FWIW: the HTTPS Everywhere issue is: https://trac.torproject.org/projects/tor/ticket/23359.
It's impossible access the…
It's impossible access the options / dashboard of uBlock, the symbol is gone too. Which means it can't be customized anymore. No way to add filters or make exceptions.
Please tell me that's a bug and not a 'feature'
Is this in a Tails context…
Is this in a Tails context or does this happen with a vanilla Tor Browser as well?
I assumed it to be an issue…
I assumed it to be an issue of Tor Browser itself but you are correct, it's only Tails, sorry.
Tor is being blocked by the…
Tor is being blocked by the City of Brampton in Canada public wireless access. The pubkic IP is 192.82.150.249. the Tor browser isn't able to ocmplete its inital connection when opened. Previously Tor browser would time out and give an option to capture logs to the clipboard but that no longer happens. The Tor browser just sits with no progress bar information.
Have you tried to configure…
Have you tried to configure bridges to circumvent the blocking? See: https://tb-manual.torproject.org/en-US/circumvention.html.
Maybe try setting Tor to use…
Maybe try setting Tor to use common ports like 80,443 only.
search for bridges outside…
search for bridges outside US. You can set up your own VPN in a virtual GNU/Linux image and run it from an online host service or pay for VPN (using cash cards, crypto currency). Do some homework first. Connect to wireless (not your own) with WIFI dongle, fake MAC and IP, use Tor to connect to the VPN. You are going to need to read up on proxy and SSH tunneling etc. Don't then log into accounts or go acting like a clown.
is there any way to bypass…
is there any way to bypass youtube ip checker because some countries are banned from seeing videos.......
is there any way to proxy all computer connection through tor browser? seems it could happen before but not today? you can use onion buddy but not clear.
Maybe, try hooktube.com, its…
Maybe, try hooktube, its youtube without the BS.
nuff said
nuff said
hi there,…
hi there,
I am wondering whether or not the new version tor browser 7.0.10 revoked the CNNIC certificate ?
Thanks!
That version did not revoke…
That version did not revoke that cert unless Firefox 52.5.0esr did so (which I have not checked).
thank u
thank u
Did something change…
Did something change recently with Twitter and the "high" security setting in TorButton? I used to be able to set it to "high" and be able to load my Twitter feed, but now it won't load unless I set it to "medium" first, then load Twitter. Note: this is just with the feeds. I can login on Twitter fine with it set to "high" but feeds won't load.
Maybe https://trac…
Maybe https://trac.torproject.org/projects/tor/ticket/24234 ? It seems they require SVG now which is forbidden on level "high".
Thank you for this link. …
Thank you for this link. That did fix the Twitter issue and I'm glad to know of the YouTube workaround as well!
TOR RULES
TOR RULES
I am not using the Tor…
I am not using the Tor-Browser for a long time and I am no expert...
I like the Tor project and I want to participate with a relay.
I am supposed to edit the torrc-file, so
I opened the torrc file:
"# This file was generated by Tor; if you edit it, comments will not be preserved
# The old torrc file was renamed to torrc.orig.1 or similar, and Tor will ignore it"
the torrc.orig.1 opens empty with my editor.
What am I doing wrong?
for some reason all day i…
for some reason all day i have not been able to "Test Tor Network Settings" but i can access other websites other than this "Test Tor Network Settings" page .. seem all fishy to me
It seems we currently have…
It seems we currently have trouble with out infrastructure. I can't reach the check website either right now.
I use some locally hosted…
I use some locally hosted client-side javascript web apps, specifically coinb.in and bip32.org. The remotely hosted versions render correctly. But opening the same apps locally with file://, they don't render correctly and are non-functional even with no-script disabled. I'm experiencing this problem with latest TOR browser on Debian stable, Tails 3.3, and Whonix 13.
That's because of https:/…
That's because of https://trac.torproject.org/projects/tor/ticket/24052 which worked around a potential proxy bypass bug. We hope Mozilla fixes the underlying problem in a proper way without functionality loss.
Is https://check.torproject…
Is https://check.torproject.org/ down? Can not rich it. Only loads to timeout and i tried new identity many time.
It has been down for a few…
It has been down for a few hours, but is back now.
Hello again, After…
Hello again, After launching, I cannot seem to get it to test Tor Network settings. It will only do that after going to some other site first. Prior to 7.0.10, it would always check pre moving on. Any idea what has changed that function? Thank you in advance.
net speed is slow. Site…
net speed is slow. Site loads, loads not, https://vbdvexcmqi.oedi.net/ loads normal -that's new.
Only me or more generally?
Hi everybody. No_Script…
Hi everybody. No_Script plugin has list of "Untrusted" domains. The question is: whether
or not adding new URLs in this list could change my fingerprinting?
there are a white-list & a…
there are a white-list & a https tab not an untrusted domains 'choice'.
it is depending on your threat model :
- if you are not too much exposed and lived in a safe location , it should not change your fingerprint.
- if you wish be safe , do not add a domain or address site in the white-list and add it on the https list.
- as soon as you change the settings -about:config- (bookmarks & white-list included) it could be revealed using sophisticated 'hack' so it is not recommended (fingerprint).
You must set no-script & https & tor settings & cookies & search browser before using Tor Browser according on your wishes.
Hi again. Thanks. I'm…
Hi again. Thanks. I'm appreciating your reply. It seems like I need to clarify the case.
There is "noscript.showUntrusted" option at the "about:config" settings. If you toggle it on there would appear "Untrusted" line at the No_Script dropdown menu. By marking web addresses and domains as "Untrusted" you could compose your own blacklist (for example : Mark torproject.org as Untrusted ; Mark vbdvexcmqi.oedi.net as Untrusted ; Mark https://vbdvexcmqi.oedi.net as Untrusted ). That list would be stored at the "about:config" "noscript.untrusted user_set string (whatever you add)" line.
Eventually you could ended up with huge and unique scroll.
My question was about that.
But how could I determine whether my location is safe or not? And what do you mean : "too much exposed"?
"You must set no-script & https & tor settings & cookies & search browser before using Tor
Browser according on your wishes."
Could you suggest such safe settings, please?
TOR inhibits, terribly much…
TOR inhibits, terribly much slow !! Long enough, very slow!
Unexpectedly long loads any page, more than ten minutes I can not wait.
What to do??
I want to get the latest…
I want to get the latest version of Tor expert bundle, but didn't see any download link via Tor official webiste. Where can I find it?
Thanks a lot.
On https://www.torproject…
On https://decvnxytmk.oedi.net/download/download.html.en clicking on the Windows option and scrolling down should give you a purple button for downloading the expert bundle. The current one can be found at https://decvnxytmk.oedi.net/dist/torbrowser/7.0.10/tor-win32-0.3.1.8.zip.
Hi there, …
Hi there,
Thanks !
I am wondering would it be possile to download Tor expert bundle via a link where I can find all the older builds and its signature? something like this: https://www.virtualbox.org/wiki/Download_Old_Builds_5_0
If this is not possbile, could you provide a link where I can download expert bundle version 0.3.0.10/ 0.3.11 with its signature?
Many thanks in advance.
We have everything archived…
We have everything archived at https://archive.torproject.org/tor-package-archive/torbrowser/. Unfortunately the expert bundles are buried in the respective Tor Browser releases. For 0.3.0.10 this would be:
https://archive.torproject.org/tor-package-archive/torbrowser/7.0.4/
I assume you meant 0.3.0.11? We did not build that one but rather switched to 0.3.1.7 directly it seems.
Pulseaudio sound does not…
Pulseaudio sound does not work with Tor Browser, but it does with Firefox. Running with --verbose shows error in console:
Failed to create secure directory (/home/someuser/.config/pulse): Permission denied
Stopping pulseaudio and trying to use apulse libs gives error:
[apulse] [error] do_connect_pcm: can't get initial hw parameters for playback device "default". Error code 1 (Operation not permitted)
[apulse] [error] do_connect_pcm: failed to open ALSA device. Apulse does no resampling or format conversion, leaving that task to ALSA plugins. Ensure that selected device is capable of playing a particular sample format at a particular rate. They have to be supported by either hardware directly, or by "plug" and "dmix" ALSA plugins which will perform required conversions on CPU.
Workarounds suggested by apulse have no effect.
And with pulseaudio not running, firefox sound doesn't work either, but other ALSA apps work fine.
Does it help to adjust the…
Does it help to adjust the permissions of /home/someuser/.config/pulse? What are those permissions right now?
The current permissions are…
The current permissions are rwx------ (700) owned by someuser. No effect on changing them to 777.
It must be related to its…
It must be related to its sandbox, although it refuses to print any sandbox debug messages. How do you whitelist access to pulseaudio or the ALSA device apulse is trying, or work around it?
You can test whether it is…
You can test whether it is really sandbox related by changing the
security.sandbox.content.levelpreference.0disables it altogether and1makes it less strict.If you run Debian you should…
If you run Debian you should now that devs recompiled their firefox with alsa support, but TBB devs decided to not follow Debian way--they use upstream version of firefox, where alsa support is disabled during compilation.
It is not straightforward to get PulseAudio (PA) runnning on any normal secure system. I think that if not yet, very soon PA will not work on any Linux system without systemd installed (btw, Devuan was forked from Debian just to get good system without systemd and dbus). So, if you follow classic UNIX secure way, soon or later you will loss sound support in TorBrowser forever. Sad, but true.
I had the same problem, so I tried to get PA with SysV working. I didn't get sound working in TBB even with PA running. Anyway, moving to systemd and PA to get sound working is as awful as moving to proprietary closed source software.
I use few different…
I use few different torbrowsers with slightly different set of preferences (all of them are using the same system tor on my Linux machine). I update them manually by checking PGP signatures in safe evironment. After each new TBB release I need to run each torbrowser in safe and clean environment and change few preferences to get working clean copy (so, I can always rollback to it after any of my torbrowser sessions). I don't need to change too many options, it is just about 5 preferences: proxy server, default search engine, default home page (blank), disable autoapdate, adjusting security slider... However, it takes too much time to create new clean torbrowsers, so I decided to write my own script for this work.
As I understood from google, the most reliable way to make changes to firefox/torbrowser preferences is to create new
user.jsfile on the same profile directory asprefs.jsfile (Am I right?). The next thing I need is to figure out what are the options I need to add touser.jswhich will make the same effect as manual editing of preferences in torbrowser interface.After first start of torbrowser the file
prefs.jsis created. At the second start I can make some changes to preferences and see what is changed inprefs.js. This way worked well for many options, but not for all of them. It looks like firefox stores inprefs.jsa lot of stuff including very minor things such as "when particular preferences were applied," "which things were already clicked in interface," etc. For me, exact set of options inprefs.jsis not well predictable. I also understand that in some future the names of preferences and behavior of torbrowser may change, so I need to track it.My particular questions in relation to this script:
1). Disabling tor-launcher through variables "TOR_SKIP_LAUNCH=1 TOR_SKIP_CONTROLPORTTEST=1 ./start-tor-browser" works well, but I would like to disable this addon completely (as in preferences of torbrowser). Is there any way to do it in script before starting TBB? Well, there is option:
user_pref("extensions.enabledAddons", "torbutton%40torproject.org:1.9.7.10,%7B972ce4c6-7e08-4474-a285-3208198ce6fd%7D:52.5.0");
However, in order to to use it, as I see, at each update I need to manually write versions of torbutton and other extensions. Can it be done simpler?
2). I need to change my default search engine from DuckDuckGo to DuckDuckGoOnion. How can I do that? It is realted either to file
search.json.mozlz4or very long and hard to parse line inprefs.js(which deals with the HTTPS Everywhere, probably). I didn't find any way to solve this problem.3). Since I update TBB manually, I disable the following update options:
user_pref("app.update.enabled", false);
user_pref("app.update.auto", false);
user_pref("app.update.backgroundErrors", 1);
Is it correct? I mean, is it the same as choosing "never check for updates" in "prefereces - advanced - update"?
4). By comparing changes done from interface and from command line I noticed that in the first case
prefs.jsincludes also these lines:user_pref("extensions.ui.dictionary.hidden", true);
user_pref("extensions.ui.experiment.hidden", true);
user_pref("extensions.ui.locale.hidden", true);
and
user_pref("gfx.blacklist.canvas2d.acceleration", 4);
user_pref("gfx.blacklist.canvas2d.acceleration.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.blacklist.direct2d", 4);
user_pref("gfx.blacklist.direct2d.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.blacklist.direct3d11angle", 4);
user_pref("gfx.blacklist.direct3d11angle.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.blacklist.hardwarevideodecoding", 4);
user_pref("gfx.blacklist.hardwarevideodecoding.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.blacklist.layers.direct3d10", 4);
user_pref("gfx.blacklist.layers.direct3d10-1", 4);
user_pref("gfx.blacklist.layers.direct3d10-1.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.blacklist.layers.direct3d10.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.blacklist.layers.direct3d11", 4);
user_pref("gfx.blacklist.layers.direct3d11.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.blacklist.layers.direct3d9", 4);
user_pref("gfx.blacklist.layers.direct3d9.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.blacklist.layers.opengl", 4);
user_pref("gfx.blacklist.layers.opengl.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.blacklist.stagefright", 4);
user_pref("gfx.blacklist.stagefright.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.blacklist.webgl.angle", 4);
user_pref("gfx.blacklist.webgl.angle.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.blacklist.webgl.angle", 4);
user_pref("gfx.blacklist.webgl.angle.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.blacklist.webgl.msaa", 4);
user_pref("gfx.blacklist.webgl.msaa.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.blacklist.webgl.opengl", 4);
user_pref("gfx.blacklist.webgl.opengl.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.blacklist.webrtc.hw.acceleration", 4);
user_pref("gfx.blacklist.webrtc.hw.acceleration.decode", 4);
user_pref("gfx.blacklist.webrtc.hw.acceleration.decode.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.blacklist.webrtc.hw.acceleration.encode", 4);
user_pref("gfx.blacklist.webrtc.hw.acceleration.encode.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.blacklist.webrtc.hw.acceleration.failureid", "FEATURE_FAILURE_OPENGL_1");
user_pref("gfx.font_rendering.opentype_svg.enabled", false);
I don't understand the origin of this options, because clean torbrowser doesn't add them in
prefs.jsafter the first start, but they are added if I do my changes through torbrowser interface (but not added, if I do it using commandline). So, should I add these options to myuser.jstoo? Are they essential?I have core file for this…
I have core file for this version of firefox. I think that after visiting one page with JS, scripts killed browser before it could ask user to stop scripts. I visited the same links again but crash didn't happen. What can I do with this core? It is about 0.5GB big (non-compressed). Which backtrace are you interested in? How can I send it to you? Tell me which commands to type in gdb (Linux, 64bit).
https://trac.torproject.org…
https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/Hacking#Ge… has some tips regarding debugging core files. I guess the whole GDB section in that document is relevant for you. You can send the results to me if you want: gk[@]torproject[.]org (without the brackets). Thanks!
Yes, I used that wiki to get…
Yes, I used that wiki to get core file. Your link tells me vague thing:
I am not familiar with the debugging and firefox internals, I don't know what is meant exactly by "stack trace" which is wanted. Google tells me it can be either of commands:
(gdb) bt
(gdb) bt full
(gdb) info threads
(gdb) thread apply all bt
(gdb) thread apply all bt full
When I run
gdb ./firefox /path/to/coreI get:GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
...
Reading symbols from ./firefox...Reading symbols from /path/to/tor-browser_en-US/Browser/.debug/firefox...done.
done.
warning: core file may not match specified executable file.
[New LWP 1620]
[New LWP 1631]
[New LWP 1652]
[New LWP 1642]
[New LWP 1648]
[New LWP 1623]
[New LWP 1624]
[New LWP 1625]
[New LWP 1626]
[New LWP 1627]
[New LWP 1628]
[New LWP 1630]
[New LWP 1634]
[New LWP 1640]
[New LWP 1641]
[New LWP 1643]
[New LWP 1649]
[New LWP 1688]
[New LWP 2483]
[New LWP 1616]
[New LWP 1633]
[New LWP 1632]
[New LWP 1629]
Core was generated by `/path/to/tor-browser_en-US/Browser/plugin-container -greom'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0000555555559225 in ?? ()
(gdb) bt full
#0 0x0000555555559225 in ?? ()
No symbol table info available.
#1 0x0000000000000003 in ?? ()
No symbol table info available.
#2 0x00007ffff3c9ba86 in ?? ()
No symbol table info available.
#3 0x0000000000000000 in ?? ()
No symbol table info available.
(gdb) bt
#0 0x0000555555559225 in ?? ()
#1 0x0000000000000003 in ?? ()
#2 0x00007ffff3c9ba86 in ?? ()
#3 0x0000000000000000 in ?? ()
(gdb)
I guess that the error is in some firefox subsystem which I have no "symbol tables" for, i.e. my core file is mostly useless. Anyway, compressed core file is about 40 MB long, I can upload it somewhere for you. Do you want it?
I got some new crash. When I…
I got some new crash. When I am in original session yet, if I print
btorbt full, it gives meaningful trace. I thought I can always reprint it again by exiting and later runninggdb /path/to/firefox /path/to/coreagain withbtcommand, but... it seems it is not so! Output after restart ofgdbis completely different. Can I get original meaningful stacktrace? I am not experienced with debugging orgdb.unable to access the website…
unable to access the website https://www.lifewire.com/free-and-public-dns-servers-2626062
How can I reproduce that? It…
How can I reproduce that? It works for me right now.
The screen comes up with…
The screen comes up with some URls then I clcik on noscript to temporary allow and then goes blank on a Torbrowser running on a Mac OSx. running through TOR relay Nickname
xorox
OR Addresses
37.187.94.86:443
I see. I assume you are…
I see. I assume you are using the security slider set to "High" and are allowing scripts if needed on particular sites, right? The problem in your case is that the mode "High" is blocking more than just scripts and it is sometimes not enough to just enable them. In this case you would need to allow SVG content as well to get the page rendered which is forbidden on the highest security level. To test whether that really makes a difference for you open
about:configand setsvg.in-content.enabledtotrue.красота
красота
this version of tor browser…
this version of tor browser won't allow clicking "sort by"
http://store.steampowered.com/search/sort_by
all other browsers allow
What exactly does not work?…
What exactly does not work? I can click on the item next to it which is a drop down menu and select items from it and the sorting gets done according to the selected category.
when clicking to sort it…
when clicking to sort it opens the web page http://store.steampowered.com/search/sort_by instead of opening the drop down menu
instead of the drop down…
instead of the drop down menu it loads the page
http://store.steampowered.com/search/sort_by
Hm, I still don't understand…
Hm, I still don't understand your problem. Are you saying you don't have this drop down menu? Or just clicking on it does not work?
How can I reproduce your problem? What operating system are you using? Did you adjust your security slider to a higher level? If so, which one? What Tor Browser version are you using?
The drop down menu doesn't…
The drop down menu doesn't appear. Clicking on it loads a web page instead of opening a drop down menu.
The operating system is Windows
The Tor Button Security Settings says "Your custom browser preferences have resulted in unusual security settings. For security and privacy reasons, we recommend you choose one of the default security levels." There's no slider.
The Tor Browser version is 7.0.10
Could you reset those…
Could you reset those settings and then test with the slider on the lowest level? Do you get the same result?
Reset the settings and…
Reset the settings and tested with slider on lowest level has same result.
Printing to PDF on Linux…
Printing to PDF on Linux does not work, it goes through the motions but no file is written.
That's probably https://trac…
That's probably https://trac.torproject.org/projects/tor/ticket/23016 and/or https://trac.torproject.org/projects/tor/ticket/23970. We'll test the fix in the next regular alpha release. Hopefully we can include it in Tor Browser 7.5 which is due in Jan 2018.
Only usability fixes in FF52…
Only usability fixes in FF52.5.1esr?
No. Mozilla is not making…
No. Mozilla is not making releases on the ESR series to fix just usability issues.
Ok but there are…
Ok but there are releasenotes for FF57.0.1 with "Various security fixes" only.
No releasenotes, no Various security fixes for 52.5.1. May later?
There are no advisories for…
There are no advisories for 57.0.1 because 52.5.1esr never made it to the release channel. There will be a 57.0.2 and a 52.5.2esr out there shortly with the usual advisories detailing more than just "Various security fixes".
don
Hmmmmm
Every captcha on every page…
Every captcha on every page doesn't work. Any help?
boycott sites that use capcha
boycott sites that use capcha
Canada's Brampton wireless…
Canada's Brampton wireless is blocking Tor while I was using public IP 192.82.150.249 on a Mac. I have it set to use ports 80 and 443 and I tried All transport types, OBFS4 ,OBF3,meek-azure and meek-amazon. And I still can not connect. Below is the log showing connection problem.
30-11-2017, 19:01:07.100 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
30-11-2017, 19:01:07.100 [NOTICE] Opening Socks listener on 127.0.0.1:9150
30-11-2017, 19:01:07.100 [NOTICE] Bootstrapped 80%: Connecting to the Tor network
30-11-2017, 19:01:07.100 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop
30-11-2017, 19:01:07.100 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '154.35.22.9:12166' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '154.35.22.12:4304' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '37.218.245.14:38224' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '37.218.240.34:40035' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '109.105.109.165:10527' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '154.35.22.13:16815' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '154.35.22.11:16488' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '109.105.109.147:13764' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '154.35.22.10:15937' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '83.212.101.3:50002' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:01:08.300 [WARN] Could not make a one-hop connection to $00DC6C4FA49A65BD1472993CF6730D54F11E0DBB. Discarding this circuit.
30-11-2017, 19:01:08.300 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:01:08.300 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:01:08.300 [WARN] Proxy Client: unable to connect to 154.35.22.11:80 ("general SOCKS server failure")
30-11-2017, 19:01:08.300 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
30-11-2017, 19:01:08.300 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:01:08.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:01:09.000 [WARN] Proxy Client: unable to connect to 154.35.22.11:80 ("general SOCKS server failure")
30-11-2017, 19:01:09.000 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
30-11-2017, 19:01:09.100 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:01:45.500 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:02:06.600 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:02:06.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:02:08.200 [WARN] Proxy Client: unable to connect to 154.35.22.9:443 ("general SOCKS server failure")
30-11-2017, 19:02:08.200 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:02:08.200 [WARN] Proxy Client: unable to connect to 192.99.11.54:443 ("general SOCKS server failure")
30-11-2017, 19:02:09.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:09.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:02:10.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:10.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:02:11.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:11.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:02:23.300 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:02:39.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:39.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:02:40.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:40.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:02:41.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:41.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:02:42.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:42.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:02:43.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:43.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:02:44.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:44.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:05.300 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:03:06.900 [NOTICE] Ignoring directory request, since no bridge nodes are available yet.
30-11-2017, 19:03:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:03:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:03:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:03:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:03:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:03:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:03:08.000 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:03:08.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:03:10.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:10.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:11.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:11.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:11.900 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
30-11-2017, 19:03:11.900 [WARN] Proxy Client: unable to connect to 154.35.22.11:80 ("general SOCKS server failure")
30-11-2017, 19:03:12.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:12.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:12.900 [WARN] Proxy Client: unable to connect to 154.35.22.11:80 ("general SOCKS server failure")
30-11-2017, 19:03:12.900 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
30-11-2017, 19:03:13.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:13.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:41.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:41.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:42.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:42.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:43.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:43.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:44.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:44.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:45.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:45.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:46.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:46.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:04:06.900 [WARN] Cannot make an outgoing begindir connection without a remote ORPort.
30-11-2017, 19:04:10.100 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:04:11.900 [WARN] Proxy Client: unable to connect to 154.35.22.9:443 ("general SOCKS server failure")
30-11-2017, 19:04:12.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:04:13.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:05:14.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:06:06.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:06:16.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:06:17.000 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:06:17.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:06:20.700 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:06:20.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:06:22.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:06:59.400 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:07:08.600 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:07:18.800 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:07:47.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:07:49.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:07:51.400 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:07:51.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:07:52.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:07:53.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:07:54.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:08:08.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:08:48.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:08:51.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:08:52.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:08:53.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:08:55.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:08:57.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:09:01.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:09:34.300 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:09:50.000 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:09:54.600 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:10:50.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:10:54.600 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:10:55.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:10:56.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:10:57.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:10:58.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:11:07.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:11:09.100 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:11:54.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:12:00.600 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:12:01.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:12:03.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:12:05.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:12:42.300 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:12:55.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:13:00.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:13:01.100 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:14:01.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:14:03.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:14:05.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:14:07.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:14:08.200 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:14:08.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:14:09.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:14:10.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:15:04.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:15:11.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:15:13.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:15:14.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:15:16.200 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:15:17.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:15:19.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:15:56.300 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:16:13.000 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:16:15.100 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:17:07.000 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:17:08.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:17:09.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:17:10.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:17:11.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:17:12.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:17:13.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:17:13.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:18:07.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:18:09.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:18:10.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:18:11.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:18:13.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:18:14.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:18:15.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:18:52.300 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:19:08.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:19:11.200 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:19:12.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:19:13.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:19:13.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:19:14.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:19:15.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:19:16.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:20:10.600 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:20:42.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:20:44.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:20:45.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:20:46.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:20:48.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:20:50.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:21:07.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '154.35.22.9:12166' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '154.35.22.12:4304' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '37.218.245.14:38224' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '37.218.240.34:40035' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '109.105.109.165:10527' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '154.35.22.13:16815' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '154.35.22.11:16488' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '109.105.109.147:13764' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '154.35.22.10:15937' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '83.212.101.3:50002' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:21:08.000 [WARN] Could not make a one-hop connection to $00DC6C4FA49A65BD1472993CF6730D54F11E0DBB. Discarding this circuit.
30-11-2017, 19:21:08.000 [NOTICE] We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish.
30-11-2017, 19:21:08.000 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:21:08.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:21:08.000 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:21:08.000 [WARN] Proxy Client: unable to connect to 154.35.22.11:80 ("general SOCKS server failure")
30-11-2017, 19:21:08.000 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
30-11-2017, 19:21:27.300 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:21:44.100 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:21:46.100 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:22:05.100 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:22:08.000 [WARN] Proxy Client: unable to connect to 154.35.22.9:443 ("general SOCKS server failure")
30-11-2017, 19:22:08.000 [WARN] Proxy Client: unable to connect to 192.99.11.54:443 ("general SOCKS server failure")
30-11-2017, 19:22:18.600 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:22:19.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:22:20.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:22:45.000 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:23:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:23:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:23:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:23:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:23:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:23:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:23:07.900 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
30-11-2017, 19:23:07.900 [WARN] Proxy Client: unable to connect to 154.35.22.11:80 ("general SOCKS server failure")
30-11-2017, 19:23:08.900 [WARN] Proxy Client: unable to connect to 192.99.11.54:443 ("general SOCKS server failure")
30-11-2017, 19:23:08.900 [WARN] Proxy Client: unable to connect to 154.35.22.9:443 ("general SOCKS server failure")
30-11-2017, 19:23:09.000 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
30-11-2017, 19:23:09.000 [WARN] Proxy Client: unable to connect to 154.35.22.11:80 ("general SOCKS server failure")
30-11-2017, 19:23:18.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:23:21.400 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:23:22.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:23:23.000 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:23:46.000 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:23:51.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:23:53.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:24:06.000 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:24:10.000 [WARN] Proxy Client: unable to connect to 154.35.22.9:443 ("general SOCKS server failure")
30-11-2017, 19:24:19.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:24:30.100 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:24:54.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:24:56.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:24:58.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:24:58.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:24:59.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:25:00.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:25:01.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:25:05.100 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:25:55.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:26:56.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:26:58.800 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:26:59.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:27:00.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:27:01.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:27:03.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:27:05.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:27:42.100 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:27:58.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:28:01.000 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:28:06.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:28:08.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:28:09.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:28:10.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:28:11.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:28:12.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:28:13.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:29:07.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:30:08.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:30:09.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:30:11.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:30:13.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:30:13.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:30:15.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:30:17.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:30:54.300 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:31:11.000 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:31:13.200 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:31:18.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:31:20.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:31:21.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:31:22.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:31:23.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:31:24.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:31:25.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:31:47.400 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
30-11-2017, 19:31:47.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
30-11-2017, 19:31:47.400 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
30-11-2017, 19:31:47.900 [NOTICE] Delaying directory fetches: DisableNetwork is set.
is there a reason for…
is there a reason for delaying 7.0.11 release?
TBB 7.0.11 from /~gk/builds is running fine.
Yes, there are actually two…
Yes, there are actually two.
1) We wanted to pick up the new Tor security update.
2) We need to pick up a new Firefox (52.5.2esr) as one of the patches included in 52.5.1esr (which we picked up in the build you mention) seems to be not ready for release yet. It's causing test failures which still need to get investigated.
That said we hope to have new Tor Browser releases out tomorrow (we already built the new alpha and are currently signing it).
TBB is again crashing at…
TBB is again crashing at google maps (almost immediately, almost reproducible). Is it something knew and known? Is it regression within the ticket 16771? If it is know, I'll send you my backtrace.
We don't have other similar…
We don't have other similar reports so far. So, that's a new thing we need to investigate.
Please explain:…
Please explain:
1) how to remember passwords in TOR;
2) how to start TOR with previous tabs.
Thanks.
These are probably disabled…
These are probably disabled to try to make you more secure. Probably they can be turned back on somewhere in the settings.
I find it wired that firefox…
I find it wired that firefox reproducibly crashes on some web pages if and only if it is run in debugger. What does it mean?
When going for bridges …
When going for bridges "https://bridges.torproject.org/" it shows bridges for scramblesuit and FTE but these types do not exist for the Mac OS version of Tor browser? Can you tell me why?
Yes. The layout of the FTE…
Yes. The layout of the FTE files is not compatible with macOS' code signing requirement. We have https://trac.torproject.org/projects/tor/ticket/18495 for fixing that. There are no Scramblesuit default bridges anymore as the one we had sipped could not keep up with the load, see: https://trac.torproject.org/projects/tor/ticket/21536.
That said you should be able to run Scramblesuit bridges in Tor Browser nevertheless.
Why comments to recent tor…
Why comments to recent tor blog news, e.g. "New stable Tor releases, with security fixes" are disabled here?
https://browserleaks.com…
https://browserleaks.com/social
https://www.trackoff.com/en
I have never had a Flickr account ever!!!
Running 7.0.10 32bit on linux
Installed fresh 2 days ago
No extra addons
Security slider on high from the start
Got the problem with this…
Got the problem with this tor version (0.3.1.9):
Dec 06 02:03:03.000 [notice] Heartbeat: Tor's uptime is XX:XX hours, with XX circuits open. I've sent XX.XX MB and received XX.XX GB.
Dec 06 02:03:03.000 [notice] Average packaged cell fullness: 65.XXX%. TLS write overhead: 4%
Dec 06 02:03:03.000 [notice] Diagnostic for issue 8387: Found 1 one-hop circuits more than 1800 seconds old! Logging 1...
Dec 06 02:03:03.000 [notice] #0 created at 2017-12-06 01:10:06. open, General-purpose client. Not marked for close. Package window: 1000. usable for new conns. Dirty since 2017-12-06 01:56:04 (4XX seconds vs 600-second cutoff).
Dec 06 02:03:03.000 [notice] It has been 2 seconds since I last called circuit_expire_old_circuits_clientside().
Added my comment to ticket 8387.
Thanks!
Thanks!
I'm unable to view most…
I'm unable to view most California-based news organizations, including LA Times, and KTLA, as well as some Europeans ones, including BBC, using TOR.
Only https://ixquick-proxy.com/ works from Startpage.
Anyone experiencing similar issues?
If JS is enabled, this test …
If JS is enabled, this test tells me that I have:
Is 984 safe value? Or is this test just wrong?
I'd say the test is not…
I'd say the test is not wrong. It measures your srollbar thickness. That currently gives away your platform at least. We are working on fixing that, though (see: https://trac.torproject.org/projects/tor/ticket/22137 for details).
Thanks. Georg! Good to know…
Thanks, Georg! Good to know it. I'll wait for the fix.
Hi. Just before there's an…
Hi. Just before there's an avalanche of YouTube related questions: YouTube did a thing again. In order to use their site, Tor users would have to set their security setting to middle (temporarily).
This might not at all be the smartest or most secure way to do it, but it is a way.
Hope this will help someone and have a nice day.
webgl.disable-angle;true…
webgl.disable-angle;true
dom.indexedDB.enabled;false
is this ok until 7.0.11 release?
Hello , Every time I…
Hello , Every time I attempt a new Tor circuit, the initial hookup stays the same: from me to C.R. (31.31.73.222), etc. WTF? This has remained like this for the most part, for three days. It feels wrong. Is it anything?
If the internet connection…
If the internet connection goes down while connecting, you enter a world of bing noises and message boxes where you are told that the connection can't be established, and there is no quit option, just an ok button which tries again and fails. Again and again forever. Even though you've fixed the problem and reconnected.
Maybe someone would like to look into the possibility of: If Internet = OK, connect; if No Internet, stop the fucking endless loop and trigger Task Manager allowing a nasty forced termination. Or just self-destruct with a please restart the program message.
Thank you otherwise for a near-flawless program.
(No subject)