New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
browser can't be downloaded because of invalid SSL certificate #254
Comments
I have seen this as well. Restarting the launcher fixed the problem. I can see many problems with this bug:
I am particularly concerned that the user is being informed that he/she "may be under attack". I think this is a mischaracterisation of how tor works: if the user able to build a circuit (which seems to be the case here), then the exit node is not supposed to know who he/she is, unless the tor network is compromised in a novel way, or some very powerful actor is running a correlation attack. It is way more likely this is a rogue exit node. I recommend the following measures be taken:
Regarding the last point: in my case, my torbrowser was up to date. Failing to start was a mistake, in this specific case: I had it started the day before and it was unlikely to be out of date in the first place. It was better, in my case, to start with an older version than to completly crash. I should note that torbrowser-launcher is the first piece of software I have seen that completely fails to start when out of date. This kind of "time bomb" technique is generally frowned upon, for good reasons: up to date is good, but it should degrade correctly. Also keep in mind warning fatigue is a problem. We keep making the mistake to tell users "they are under attack", and our users have come to ignore those warnings, with good reasons sometimes. Anyone that has actually been attacked by a fellow human being will, at the best of times, laugh at those ridiculous warnings, and rightly so ignore them. At the worst of times, they will relive, for an instant, that traumatic moment and hate our software for reminding them of that terrible moment. Note that this was also reported in the Debian BTS (#845989). |
I can't reproduce. Is this still an issue? |
micahflee, I get this error on Ubuntu 16.04 32 bit architecture and on Windows bash Ubuntu 16.04 64 bit architecture. No matter how many times I uninstall and reinstall or retry it I always get this error. It is possible however to install the Tor Browser bundle directly from the website using other methods in both Ubuntu 16.04 32 bit and Windows 10 Bash Ubuntu. |
I can still reproduce this in Debian Jessie (see above BTS link), but maybe this could be considered a Debian-specific issue at this point... :/ |
For those who are still facing the issue, run this:
And restart |
For me the only thing that worked was this:
|
|
As per https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845989 :
|
|
I tried these https://github.com/micahflee/torbrowser-launcher instructions: « If you want to always have the latest version of the torbrowser-launcher package before your distribution gets it, you can use my PPA: sudo add-apt-repository ppa:micahflee/ppa The log is below:
|
I've had the same problem when I tried downloading it from an organization free wifi. |
Worked for me too |
Trying to start torbrowser for the first time produce the following message
After that the program terminate. Running it from terminal results in the
following console output:
The text was updated successfully, but these errors were encountered: