Re: [tor-relays] Comcast blocks ALL traffic with tor relays

Subject: Re: [tor-relays] Comcast blocks ALL traffic with tor relays

From: xmrk2 via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx>

Date: Wed, 14 Jun 2023 19:09:43 +0000

Cc: xmrk2 <xmrk2@xxxxxxxxxxxxxx>, tor-relays@xxxxxxxxxxxxxxxxxxxx

Delivery-date: Wed, 14 Jun 2023 15:13:51 -0400

Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=lists.torproject.org; s=2022-eugeni; t=1686769992; bh=+MVOnhyUATOgruZwtTj/X9QMQSSmzntR194qJZCeegg=; h=Date:To:In-Reply-To:References:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=C+NIMNMz0bQJzyQxtWqW8GOhzJrf6NCk9hv0CJa5ojjlbsjEcfWnLDBzzRErhaduE 9V970aaa5gQ0KBEvsGI378HgZrFfq62Eqt99C2+h1Mqd+8pdYuExm3OB3zG0IoQgp7 LmQTqsT3q3SPm7eJM/AHLWbSXg3lKa7SelU/QBmH1r3gh7N7AhJPLfQWCaKWSdc1s0 thAMhlLZ9iBJ8R0spfEh2zKJPgVH0GhUPg4N0fhoVcI6yxprDhH9og6qlb4BoYEQDN kNKmDPLkE+aYueoINvE3CrOv9XPs5iHCFxnn2DsevcaHeBVJRcgcbHl7exGAqkQpWH t9Fv6X4Iu3M0w==

Feedback-id: 43685724:user:proton

In-reply-to: <5FD36BAD-C471-4888-B0EA-33DC93B3EDF7@gmail.com>

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: <n7SJf1DnK5EXU4pns-uwURzkpjSvUkt5WOrc1J7Z2pfebu9GTA0cflcJInDlQAaGvdzsFPFansqD4lZBjgmu2trhNptdQ1_J-pU4RfIX_9E=@protonmail.com> <5FD36BAD-C471-4888-B0EA-33DC93B3EDF7@gmail.com>

Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx

Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>

I have only experienced similar problems while running tor exit node, even with very restricted exit policy. Allowing exit only to port X, and unable to initiate connections to port Y (typically Y=HTTPS=443, of course X =/= Y).

Note that those problems are not Comcast's fault, although they do point to more general problem: that people (webmasters, cloud services, ISPs) sometimes block too much and misunderstand tor, they probably wanted to block just tor exits, but end up blocking anything tor-related.

This leads me to following idea: Educational campaign to teach relevant people about difference between middle relays and exits. My proposal for title/slogan: "Tor relays are not a threat - no reason to block them". (Should it be "middle relays"? But it seems too long then.) EFF could be quite helpful there.

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