- tor-onions - lists.torproject.org

Tor transport protocol test results
by Michael Jonker 20 Mar '18

20 Mar '18

Thanks again for the helpful info from the last time I asked this list a question. I have built some tests comparing WebSockets, Request-Response and gRPC (basically http/1.1 vs http/2) over TOR and you can view them live here: http://flhqvb2425keopts.onion or http://oniontests.openpoint.ie The testing code is on Github: https://github.com/citkane/onion-tests I would be most interested if any logic flaws in the tests are identified and / or any suggestions of additional testing. (If so, issues on Github would be my preferred communication channel).

1 0

(no subject)
by chara undertale TV 09 Mar '18

09 Mar '18

Subscription

1 0

Connection to a hidden service with a RFC 6455 web-socket - advice on risks please
by Michael Jonker 07 Mar '18

07 Mar '18

I have connected to my hidden service with RFC 6455 web-socket and feel like a kid in a candy store streaming API requests and return data back and forth at good, reliable speeds. My concern is that I am missing something here..... My mental model is that, once the connection and http upgrade request is established, TOR sees this as a long running http request and will will not close the circuit or change the route until the either side breaks the connection. I would appreciate if someone could comment: 1) Am I correct in my mental model? 2) Am I perpetrating a security anti-pattern by holding the connection open indeterminately? Thanks in advance.

4 7

Re: [tor-onions] DDoS, Single Onion Services and IP Addresses
by Alec Muffett 02 Feb '18

02 Feb '18

The current limit is 2 connections per IP address. This affects single onion services, because they don't use guards. Can you please make sure that you only have one or two Single Onion Services on each outbound IP address? I think the NYT is okay (separate IPs?) but if I understand this right, this is going to hamper EOTK development, since I have ~ 12 worker onions spread over 6 quad-core machines, and then publish up to 10 additional "service" addresses via OnionBalance ... all behind my single DSL NAT firewall that protects them from inbound traffic. Hmmm... - a

6 7

DDoS, Single Onion Services and IP Addresses
by teor 02 Feb '18

02 Feb '18

Hi All, Is this list still working? :-) One of our new DDoS defences stops Tor clients from building lots of circuits over multiple connections from the same IP address. The current limit is 2 connections per IP address. This affects single onion services, because they don't use guards. Can you please make sure that you only have one or two Single Onion Services on each outbound IP address? If you have multiple IP addresses on your machine, you can set OutboundBindAddress. Otherwise, Tor will use the default route. T

2 1

hidden server problem strange error in debug file
by robm＠riseup.net 27 Sep '17

27 Sep '17

Hello, I did set up a httpd hidden service but it is not reachable. When I try to reach it with the tor browser from my desktop the services is not available and I get this error every time I Try to access it from the tor browser: Sep 25 03:43:49.000 [info] command_process_relay_cell(): circuit_receive_relay_cell (backward) failed. Closing. I have no firewall running. tor version is Tor version 0.3.1.7. this is my torrrc: Log notice file /usr/local/log/tor/notices.log Log debug file /usr/local/log/tor/debug.log RunAsDaemon 1 DataDirectory /usr/local/lib/tor HiddenServiceDir /usr/local/lib/tor/httpd/ HiddenServicePort 80 127.0.0.1:8029 apache httpd is running on localhost port 8029 I do not know what can be wrong and why the tor circuit does not work. here is the notice.log Sep 25 03:39:20.000 [notice] Tor 0.3.1.7 opening log file. Sep 25 03:39:20.368 [warn] OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with 100020bf: OpenSSL 1.0.2k 26 Jan 2017; running with 100020bf: OpenSSL 1.0.2k-fips 26 Jan 2017). Sep 25 03:39:20.400 [notice] Tor 0.3.1.7 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2k-fips, Zlib 1.2.7, Liblzma N/A, and Libzstd N/A. Sep 25 03:39:20.400 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Sep 25 03:39:20.400 [notice] Read configuration file "/usr/local/etc/tor/torrc". Sep 25 03:39:20.405 [notice] Opening Socks listener on 127.0.0.1:9050 Sep 25 03:39:20.000 [warn] Your log may contain sensitive information - you're logging more than "notice". Don't log unless it serves an important reason. Overwrite the log afterwards. Sep 25 03:39:20.000 [notice] Parsing GEOIP IPv4 file /usr/local/share/tor/geoip. Sep 25 03:39:20.000 [notice] Parsing GEOIP IPv6 file /usr/local/share/tor/geoip6. Sep 25 03:39:20.000 [notice] Bootstrapped 0%: Starting Sep 25 03:39:21.000 [notice] Starting with guard context "default" Sep 25 03:39:21.000 [notice] Bootstrapped 80%: Connecting to the Tor network Sep 25 03:39:22.000 [notice] Bootstrapped 85%: Finishing handshake with first hop Sep 25 03:39:22.000 [notice] Bootstrapped 90%: Establishing a Tor circuit Sep 25 03:39:22.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Sep 25 03:39:22.000 [notice] Bootstrapped 100%: Done any hints ? thank you very much Rob

2 1

Re: [tor-onions] tor-onions Digest, Vol 16, Issue 1
by Nicwow 25 Sep '17

25 Sep '17

What hidden service are you trying to reach? Sent from ProtonMail Mobile On Mon, Sep 25, 2017 at 5:00 AM, <tor-onions-request(a)lists.torproject.org> wrote: > Send tor-onions mailing list submissions to tor-onions(a)lists.torproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-onions or, via email, send a message with subject or body 'help' to tor-onions-request(a)lists.torproject.org You can reach the person managing the list at tor-onions-owner(a)lists.torproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of tor-onions digest..." Today's Topics: 1. hidden server problem strange error in debug file (robm(a)riseup.net) Hello, I did set up a httpd hidden service but it is not reachable. When I try to reach it with the tor browser from my desktop the services is not available and I get this error every time I Try to access it from the tor browser: Sep 25 03:43:49.000 [info] command_process_relay_cell(): circuit_receive_relay_cell (backward) failed. Closing. I have no firewall running. tor version is Tor version 0.3.1.7. this is my torrrc: Log notice file /usr/local/log/tor/notices.log Log debug file /usr/local/log/tor/debug.log RunAsDaemon 1 DataDirectory /usr/local/lib/tor HiddenServiceDir /usr/local/lib/tor/httpd/ HiddenServicePort 80 127.0.0.1:8029 apache httpd is running on localhost port 8029 I do not know what can be wrong and why the tor circuit does not work. here is the notice.log Sep 25 03:39:20.000 [notice] Tor 0.3.1.7 opening log file. Sep 25 03:39:20.368 [warn] OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with 100020bf: OpenSSL 1.0.2k 26 Jan 2017; running with 100020bf: OpenSSL 1.0.2k-fips 26 Jan 2017). Sep 25 03:39:20.400 [notice] Tor 0.3.1.7 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2k-fips, Zlib 1.2.7, Liblzma N/A, and Libzstd N/A. Sep 25 03:39:20.400 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Sep 25 03:39:20.400 [notice] Read configuration file "/usr/local/etc/tor/torrc". Sep 25 03:39:20.405 [notice] Opening Socks listener on 127.0.0.1:9050 Sep 25 03:39:20.000 [warn] Your log may contain sensitive information - you're logging more than "notice". Don't log unless it serves an important reason. Overwrite the log afterwards. Sep 25 03:39:20.000 [notice] Parsing GEOIP IPv4 file /usr/local/share/tor/geoip. Sep 25 03:39:20.000 [notice] Parsing GEOIP IPv6 file /usr/local/share/tor/geoip6. Sep 25 03:39:20.000 [notice] Bootstrapped 0%: Starting Sep 25 03:39:21.000 [notice] Starting with guard context "default" Sep 25 03:39:21.000 [notice] Bootstrapped 80%: Connecting to the Tor network Sep 25 03:39:22.000 [notice] Bootstrapped 85%: Finishing handshake with first hop Sep 25 03:39:22.000 [notice] Bootstrapped 90%: Establishing a Tor circuit Sep 25 03:39:22.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Sep 25 03:39:22.000 [notice] Bootstrapped 100%: Done any hints ? thank you very much Rob _______________________________________________ tor-onions mailing list tor-onions(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-onions

1 0