Sounds like a great way to do it.Â
I do want to make validation against the network, specifically with the contact info however I don't think there is any validation in the network as to the values of the email and/or host.
Is there an easy way for me to get a node's public key from itself or the network? That way they can sign the fingerprintÂof the node + requested domain nameÂusing their private key and I can verify it with their public key.
Eran
Link requested subdomains to the relay's fingerprint, and require all
change/update requests to be signed by the node's keys, and have some
validation that the node can be found on the network (and is an exit
node). This will ensure only Tor exit nodes can apply, and that nodes
can only change their own subdomain, and even makes it reletively
scriptable, if desired.
On 2015-10-25 12:26, Geoff Down wrote:
> On Sun, Oct 25, 2015, at 05:49 AM, Eran Sandler wrote:
>> If so, I'll write a small something that will allow adding new
>> subdomains
>> to it. So that you can always add and update subdomains on it.
>Â As long as you don't let other people do that themselves. That would
> be
>Â open to abuse.
> GD
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays