[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-relays] Traffic in port 9050 in a relay (denial of service attack?)

To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-relays] Traffic in port 9050 in a relay (denial of service attack?)
From: Paritesh Boyeyoko <parity.boy@xxxxxxxxx>
Date: Mon, 04 Nov 2013 23:51:21 +0000
Delivered-to: archiver@xxxxxxxx
Delivery-date: Mon, 04 Nov 2013 18:51:38 -0500
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:user-agent:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=wvpDH8k016fAlBWrhwS6xKp7p4ExTuLGMBf9Dcf4+U4=; b=Y6EtKl5U7AmsyCr8UOyxrOAOGSo/MKwkENMBYqDSILnGU1JCiacbFr4RMZxGw/QZhf 64+5yvB/rMTjHkMqywQRKkJhv15jAx/nfDxPInZxx+9iibY1jSEAuf9aH9/edm/RfanQ ItvmIEiVZ9PovEMDsS/EH4J3B7JEpaPhTxCpKA6KM7PYe6ywKlHGD+XOoj+JBuGYUqgp pUQGQG0b6rZbU6wOmDdh/PLKzVsg+BktsuW6C4UL0tIz7zkzmGuqY54PW2rm812dZ3HL e+2T02IvBnLp6/6hukCT02qeUVK4OBn9MmMm6ft+AZt2VSSCFpO5gRnsQDofpNFu92SI olqw==
In-reply-to: <CAGT8D4PJXzsTzcn9qPCPYmWiXoZ2C3xbZpLhEOHHnCvZLOnz+A@xxxxxxxxxxxxxx>
List-archive: <http://lists.torproject.org/pipermail/tor-relays/>
List-help: <mailto:tor-relays-request@lists.torproject.org?subject=help>
List-id: "support and questions about running Tor relays \(exit, non-exit, bridge\)" <tor-relays.lists.torproject.org>
List-post: <mailto:tor-relays@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=unsubscribe>
References: <CAGT8D4PJXzsTzcn9qPCPYmWiXoZ2C3xbZpLhEOHHnCvZLOnz+A@xxxxxxxxxxxxxx>
Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx
Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>
User-agent: KMail/4.9.5 (Linux/3.5.0-34-generic; KDE/4.9.5; x86_64; ; )

@jj tor

If your torrc literally reads "SocksPort = 0" (no quotes) then the config parser will ignore this and fall back to the default internal setting which is port 9050 wide open.

Your torrc needs to read "SocksPort 0" (no quotes) to disable SOCKS connectivity.

Best,

Parity

parity.boy@xxxxxxxxx

_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

References:
- [tor-relays] Traffic in port 9050 in a relay (denial of service attack?)
  - From: jj tor

Prev by Author: Re: [tor-relays] Is there any reason to keep the default exit policy?
Next by Author: Re: [tor-relays] Traffic in port 9050 in a relay (denial of service attack?)
Previous by thread: [tor-relays] Traffic in port 9050 in a relay (denial of service attack?)
Next by thread: Re: [tor-relays] Traffic in port 9050 in a relay (denial of service attack?)
Index(es):
- Author
- Thread