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 - Serve port 25 (SMTP) and forwards abuse@mydomain.com to an address of your choosing
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).
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@mydomain.com 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
On 17 Nov 2015, at 17:07, Eran Sandler eran@sandler.co.il 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@mydomain.com mailto:abuse@mydomain.com 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@mydomain.com mailto:abuse@mydomain.com 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@lists.torproject.org 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
On Tue, Nov 17, 2015 at 3:21 PM Tim Wilson-Brown - teor teor2345@gmail.com wrote:
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.
Sure, I can allow turning it off. The main feature is having it pull the page from some repo that will get updated more often, so if there is an update to the page it will get pulled.
- Serve port 25 (SMTP) and forwards abuse@mydomain.com 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?
It will require an MX record. The other project I'm working on is a site that will allow to give DNS names for Tor exit nodes and will provide the DNS for these nodes. So I can give you mynode.torexitnode.net and other can run it for other domains.
It will use the network itself to verify the node and can also setup the MX records for you automatically.
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.
Sure. I will take that into account.
We can either generate all variations or have a server answer these "pull" calls based on a number of parameters that will be sent and will generate it on the fly.
Thanks, Eran
On Tue, 17 Nov 2015 13:29:30 +0000, Eran Sandler wrote: ...
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?
It will require an MX record.
Not as far as I know. When there is no MX record on mynode.torexitnode.net the A record on it will be used as the address of the SMTP server for that domain.
Or did that change some time this millenium?
Andreas
Is this in the RFC? :-)
That's the kind of logic that get bounced off new implementations...
On Tue, Nov 17, 2015 at 4:19 PM Andreas Krey a.krey@gmx.de wrote:
On Tue, 17 Nov 2015 13:29:30 +0000, Eran Sandler wrote: ...
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?
It will require an MX record.
Not as far as I know. When there is no MX record on mynode.torexitnode.net the A record on it will be used as the address of the SMTP server for that domain.
Or did that change some time this millenium?
Andreas
-- "Totally trivial. Famous last words." From: Linus Torvalds <torvalds@*.org> Date: Fri, 22 Jan 2010 07:29:21 -0800 _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays@lists.torproject.org
-
Andreas Krey -
Eran Sandler -
Tim Wilson-Brown - teor