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.
Â
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