-
Notifications
You must be signed in to change notification settings - Fork 181
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
Crash in Debian sid, related to twisted version #192
Comments
Also downstream on Fedora 21+: https://bugzilla.redhat.com/show_bug.cgi?id=1246381 . |
Installing the latest version of txsocksx from GitHub fixed this problem. Now instead of
Starting the Tor service fixes this problem as well. |
Thanks @quixotique. And eek, gotta try to fix this soon. torbrowser-launcher is marked for autoremoval from Debian testing because of this bug. I'll see if I can do it tomorrow, but then I'll be on an airplane and then at hacker conferences for a week... so it may need to wait. |
Can confirm that upgrading to @quixotique What can I try to reproduce |
I can confirm that it helps too. I can't ship my own txsocksx with torbrowser-launcher, but luckily yesterday Debian sid upgraded to python-txsocksx 1.15.0.2. It can now successfully make http requests over Tor! But now I'm running into a problem related to certificate pinning:
The crash is happening here: https://github.com/micahflee/torbrowser-launcher/blob/master/torbrowser_launcher/launcher.py#L454 And it seems like it has to do with the VerifyTorProjectCert class not implementing IPolicyForHTTPS: I'm about to head to the airport and won't be able to work on this for a week. With any luck Debian will update some more packages and the problem will just go away :) but if not any pull requests are appreciated. |
The patch in the pull request works well (tested under debian sid) and seems largely cosmetic. Since this has been breaking the debian package for quite a while (at least in sid), merging and releasing this soonish would be nice. |
Hi @niklasf, I had configured torbrowser-launcher to only check for upgrades over Tor, and I normally used Vidalia to start and stop Tor. If I launched torbrowser-launcher without starting Tor first, then I would get the "Connection refused" error. |
any updates to the patch gentleman ? |
I confirm this issue is fixed by the #196 pull-request. See how I install and patch |
Sorry I haven't merged it yet! Working on it now. |
Downstream bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793791
The text was updated successfully, but these errors were encountered: