Torsocks issueshttps://gitlab.torproject.org/tpo/core/torsocks/-/issues2021-07-09T18:32:02Zhttps://gitlab.torproject.org/tpo/core/torsocks/-/issues/8038Allow torsocks to interact with TBB in a useful way2021-07-09T18:32:02ZMatthew FinkelAllow torsocks to interact with TBB in a useful wayTBB will select a random SOCKS port, torsocks should provide a way to find/be given this port number. Asking users to retrieve it from Data/Tor/port.conf and modify torsocks.conf is nonobvious.TBB will select a random SOCKS port, torsocks should provide a way to find/be given this port number. Asking users to retrieve it from Data/Tor/port.conf and modify torsocks.conf is nonobvious.https://gitlab.torproject.org/tpo/core/torsocks/-/issues/8006Unnecessary test in torsocks script2021-07-09T18:32:02ZTracUnnecessary test in torsocks scriptTorsocks suggests running with no arguments to start a shell, however the launcher script errors when no arguments are passed. Attached patch fixes this.
**Trac**:
**Username**: dmaTorsocks suggests running with no arguments to start a shell, however the launcher script errors when no arguments are passed. Attached patch fixes this.
**Trac**:
**Username**: dmahttps://gitlab.torproject.org/tpo/core/torsocks/-/issues/7564[PATCH] Use libdir instead of prefix in torsocks wrapper2021-07-09T18:32:02ZTrac[PATCH] Use libdir instead of prefix in torsocks wrapperUse the autotools configure standard for assigning the library directory.
**Trac**:
**Username**: robinsonUse the autotools configure standard for assigning the library directory.
**Trac**:
**Username**: robinsonhttps://gitlab.torproject.org/tpo/core/torsocks/-/issues/6542curl 7.27.0 doesn't work with torsocks2021-07-09T18:32:02Zcypherpunkscurl 7.27.0 doesn't work with torsocksAfter upgrading curl to version 7.27.0, various programs that depend on libcurl (including curl itself) no longer work with torsocks.
All requests are replied to with the "501 Tor is not an HTTP proxy" message. Curiously, the first two ...After upgrading curl to version 7.27.0, various programs that depend on libcurl (including curl itself) no longer work with torsocks.
All requests are replied to with the "501 Tor is not an HTTP proxy" message. Curiously, the first two bytes of the response are 0x05 0x00 as you would expect from a valid SOCKS5 reply.
Perhaps there's some poor buffer management lurking around.
Thanks.
Software versions:
Linux 3.4.7-1-ARCH i686
curl 7.27.0
torsocks 1.2
tor 0.2.2.37David Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/tpo/core/torsocks/-/issues/6155Import torsocks from google code to torproject.org trac2021-07-09T18:32:02ZproperImport torsocks from google code to torproject.org tracReasons:
* You can not post anonymously to the google code tracker.
* You can not have an anonymous google account, since it requires verification.
* Google code is not accessible from some countries.
* It's Tor standard software, in...Reasons:
* You can not post anonymously to the google code tracker.
* You can not have an anonymous google account, since it requires verification.
* Google code is not accessible from some countries.
* It's Tor standard software, in the torproject.org repository, and you can't really keep track of it there.Robert HoganRobert Hoganhttps://gitlab.torproject.org/tpo/core/torsocks/-/issues/801Torify+dsocks: A listener connection returned a socket with a mismatched family2021-07-09T18:32:02ZTracTorify+dsocks: A listener connection returned a socket with a mismatched familyWhen i try to torify something trought dsocks-torify.sh it doesn't works.
Example:
dsocks-torify.sh nmap -P0 -v -n 1.2.3.4 -p21 -sV
Starting Nmap 4.50 ( http://insecure.org ) at 2008-08-16 13:45 CEST
Initiating Connect Scan at 13:45
Sc...When i try to torify something trought dsocks-torify.sh it doesn't works.
Example:
dsocks-torify.sh nmap -P0 -v -n 1.2.3.4 -p21 -sV
Starting Nmap 4.50 ( http://insecure.org ) at 2008-08-16 13:45 CEST
Initiating Connect Scan at 13:45
Scanning 87.29.167.157 [1 port]
nmap: (dsocks) couldn't connect to proxy at 127.0.0.1:9050
Discovered open port 21/tcp on 87.29.167.157
Completed Connect Scan at 13:45, 0.14s elapsed (1 total ports)
Host 87.29.167.157 appears to be up ... good.
Interesting ports on 87.29.167.157:
PORT STATE SERVICE
21/tcp open ftp
Nmap done: 1 IP address (1 host up) scanned in 0.204 seconds
this is the entry in the Tor debub log
[info] connection_handle_listener_read(): Bug: A listener connection returned a socket with a mismatched family. Socks listener for addr_family 2 gave us a socket with address family 0. Dropping.
i've the last version of dsocks aviable from darwinports.
Thanks to all!
bye
[Automatically added by flyspray2trac: Operating System: OSX 10.4 Tiger]
**Trac**:
**Username**: m4rco-David Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.org