- tor-onions - lists.torproject.org

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

list
by diego muc 06 Jul '17

06 Jul '17

im interesting in gay por real and pedo porn video with boys

4 3

(no subject)
by Pete Lopes 06 Jul '17

06 Jul '17

Ff

3 2

Помощь.
by Викульчик 22 May '17

22 May '17

-- Отправлено из Mail.Ru для Android

1 0

Onion Service Fixes in 0.3.0.6
by teor 28 Apr '17

28 Apr '17

Hi All, We fixed a few onion service introduction point bugs in Tor 0.3.0.6. These may have caused reachability issues for onion services, particularly single onion services. (Thanks to Alec for reporting these bugs.) https://gitweb.torproject.org/tor.git/tree/ReleaseNotes?id=47d2e4f06ec26a79… We didn't get the fix for migrating existing hidden services to single onion services in this release. I am sorry about that. I am not sure if the fix will get in before the 0.3.1 code freeze in May, it depends if I have time, or if someone else picks it up. T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------

1 0

Re: [tor-onions] [tor-talk] TOR problems - seriously PLEASE HELP ME!
by Jonathan Marquardt 24 Apr '17

24 Apr '17

On Mon, Apr 24, 2017 at 12:16:23PM +0200, unpublished wrote: > 1. Many web pages display information that I do not support "TOR > connections"? Not sure, what you mean here. Perhaps THEY don't support (i.e. block) connections from Tor users, because they are afraid of spam or other stupid reasons. Nothing you can really do here. Websites blocking Tor is a huge problem. > 2. How to increase (amazon) the number of relay nodes? Because standard > only two redirect point? There are always three nodes. The amazon node should be your guard relay (where you enter the Tor network). Then there are two relays after that. There isn't really any way to change that. Three hops should be sufficient for decent anonymity, no real need to worry here. > 3. How to change the end node of the country (eg country from which I am > POLAND)? Here's a simple guide on how to do that: http://www.wikihow.com/Set-a-Specific-Country-in-a-Tor-Browser -- 4096R/1224DBD299A4F5F3 47BC 7DE8 3D46 2E8B ED18 AA86 1224 DBD2 99A4 F5F3

1 0

[warn] connection_edge_process_relay_cell (at origin) failed
by Joe Renege 04 Apr '17

04 Apr '17

Hi! I have a hidden service on Tor 0.2.9.10 and a log file filled with: [warn] connection_edge_process_relay_cell (at origin) failed. The warnings appear about a minute after starting up and every 30 seconds afterwards. Service eventually degrades to only accepting a fraction of connections. I can only get the service completely online again with a restart. To improve uptimes I have the restart running automatically every 20 minutes. I hope there is a more elegant solution to the problem. Maybe worth saying that this only became an issue when the service started experiencing much higher traffic volume. Despite high volume the box is idling, the tor process is at about 5% CPU and there is lots of available memory.

2 1