net/torsocks gives "authentication failure" and password error. Example: $ torsocks wget www.ipmango.com/api/myip Resolving www.ipmango.com (www.ipmango.com)... 173.255.230.5 \ Connecting to www.ipmango.com (www.ipmango.com)|173.255.230.5|:80... 17:47:01 libtorsocks(28774): Need a password in torsocks.conf or $TORSOCKS_PASSWORD to authenticate withfailed: Connection refused. This is a documented problem: https://trac.torproject.org/projects/tor/ticket/9695 The solution is to upgrade to torsocks 2.0, where #9695 is fixed
Maintainer CC'd
If you had provided a patch, we could have applied it to the port without maintainer approval since he never responded. Without a patch, we can't do much when a maintainer doesn't respond.
I think this is the case of unresponsive maintainer. He didn't reply beginning Nov 2013. In 2013 1.3 version was released, and last year 2.0 was released, and package is still @1.2. John, do you think you should update MAINTAINER=ports@ ? Otherwise every action will be on hold.
yes. The maintainer didn't stage the port, somebody else did. If that had not happened, the maintainer would have been reset then. So we can consider that serious non-responsiveness at that time. Go ahead and make your patch either reset the maintainership, or better: assign yourself as maintainer.
Ok, I will make a patch in a day.
Created attachment 154781 [details] Patch to update to 2.0.0 This is patch-ready. Please note that all old patches from net/torsocks/files/ are deleted, only two files there now: > # ls net/torsocks/files/ > patch-compatibility-2.0.0 pkg-message.in patch-compatibility-2.0.0 is submitted upstream.
Created attachment 154782 [details] poudriere log
Also there is CAVEAT that firefox crashes with torsocks. And chrome and opera seem to be much more sluggish for some reason, compared to when Tor is accessed through SOCK5 directly.
looks decent, I'm promoting the PR.
The caveat I mentioned is due to the fact that torsocks fails socket(2) for UDP protocol, instead of just "losing" packets, what usually happens. Many apps, including firefox and qTox, fail to process such socket(2) error code, and crash. So this isn't a bug in torsocks, rather in the other apps due to this somewhat unique situation.
Build tests worked on 10.1a, 9.3a, failed on 8.4i. See http://people.freebsd.org/~pi/logs/net__torsocks* (some github-related fixes were necessary)
build works on 8.4a. Is this a i386 thing ?
fails on 10.1i as well, so looks like i386 thing ? http://people.freebsd.org/~pi/logs/net__torsocks-10i
Should we add ONLY_FOR_ARCHS= amd64 and commit now and investigate later ? Yuri, please ACK.
Created attachment 154970 [details] Patch to update to 2.0.0 This was a bug in upstream code. I added the patch that should eliminate i386/amd64 build difference. amd64 poudriere build passes fine. And I don't have i386 environment here to verify.
(In reply to yuri from comment #15) > amd64 poudriere build passes fine. > And I don't have i386 environment here to verify. If you have amd64 poudriere, why not just use it to make an i386 jail? With amd64, you can test i386, but not vice-versa.
A commit references this bug: Author: pi Date: Sun Mar 29 19:56:13 UTC 2015 New revision: 382623 URL: https://svnweb.freebsd.org/changeset/ports/382623 Log: net/torsocks: 1.2 -> 2.0.0 - Changes: https://github.com/dgoulet/torsocks/blob/master/ChangeLog - Submitter takes maintainership - Repository moved from google to github (and further) PR: 195715 Submitted by: yuri@rawbw.com Approved by: <andy.lavr@gmail.com> (maintainer timeout) Changes: head/net/torsocks/Makefile head/net/torsocks/distinfo head/net/torsocks/files/patch-Makefile.am head/net/torsocks/files/patch-Makefile.in head/net/torsocks/files/patch-compatibility-2.0.0 head/net/torsocks/files/patch-configure.in head/net/torsocks/files/patch-doc_Makefile.am head/net/torsocks/files/patch-src_Makefile.am head/net/torsocks/files/patch-src_Makefile.in head/net/torsocks/files/patch-src_torsocks.in head/net/torsocks/files/patch-src_usewithtor.in head/net/torsocks/files/patch-tests_Makefile.am head/net/torsocks/files/pkg-message.in head/net/torsocks/pkg-descr head/net/torsocks/pkg-plist
Tests with i386 on 10.1, 8.4 went fine. Committed, thanks! Please note that I changed pkg-descr with WWW: to github, but the final repo is now https://gitweb.torproject.org/torsocks.git