Re: [tor-relays] Tor exit node companion

Subject: Re: [tor-relays] Tor exit node companion

From: Tim Wilson-Brown - teor <teor2345@xxxxxxxxx>

Date: Wed, 18 Nov 2015 00:20:50 +1100

Delivery-date: Tue, 17 Nov 2015 08:21:11 -0500

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:message-id :references:to; bh=wIv9x6/6CZmaEv0BegiPE8o+5PpNbuq4wWgHtgC2DfY=; b=HWXYqd4H0E0QdK/t365lMqp9+uWJH6Z5K6WtV0nr1lAEZlPE4psA71n724BlAYeAVn WN1oKNk9ulUUb2UEo0cA0nEaEGTk6v9cUc9SenJqO/yUKsGC/jXVcCC6iHMuEYqv8yIT bGK8waX3D00phoOnvR/w7+F79X0pceEpkRri3ZSvrCUR/0FYuaQMWNm4gtheXbglKrz/ hnyboOvybuXxT+74dCxn/ezvhhbjm4GcfAVl39vCvu3kLIrRGW8d0160zSQ3364yB8md 7+nXNBPi0V8cuhjoSFvqIg/Zs1Vb3tk7NWmRVSONcuM8/PPmKrKy8xQlReSjGQALevmC MzEQ==

In-reply-to: <CALR3k-FjYyMNz-XktjyAH4g=fKCN8rggyL-FqUUN+eD7Gcec8Q@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: <CALR3k-FjYyMNz-XktjyAH4g=fKCN8rggyL-FqUUN+eD7Gcec8Q@xxxxxxxxxxxxxx>

Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx

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

On 17 Nov 2015, at 17:07, Eran Sandler <eran@xxxxxxxxxxxxx> wrote:

Hi guys,

I had a thought about writing a small Tor exit node companion app.

This would be a single executable that does 2 things:
Serve HTTP port 80 traffic on a specific host name and show the standard Tor web page for exit nodes

Tor already does this for the DirPort. So if a relay has a DirPort 80 configured, it would conflict with the app.

As long as the HTTP port 80 can be turned off, it could be useful.

Serve port 25 (SMTP) and forwards abuse@xxxxxxxxxxxx to an address of your choosing

Would serving port 25 also require a MX record in DNS, or do webiron and others send mail direct to the relay regardless of MX records?

Bonus points would be to make sure the HTTP requests serve the latest version of the Tor disclaimer page (so it will automatically take the latest and periodically check that its the latest). It will then replace the various parts (email of the operator etc).

This would be useful, but please note that the disclaimers vary by jurisdiction and language, so that would need to be configurable.

I can write it in Go so that its a single rather small executable so that the exit node will only need to run it instead of web server (nginx or something lighter) and an SMTP server (for those pesky automated posts that, like in the case of webiron, are also sent to abuse@xxxxxxxxxxxx based on the reserve DNS).

Do you think it would be useful? I would sure be happy to run as little processes as possible.

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

Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP 968F094B

teor at blah dot im
OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

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