Re: [tor-relays] Using ContactInfo to publish additional relay properties in a standardized way (opt-in)
Hi, On 15/10/17 09:07, nusenu wrote: >> See proposal 234 [0] for adding bitcoin/zcash/etc addresses. > > Thank you for the pointer. This proposal is from 2014 and I havn't found > any trac ticket for it, so I guess no one is working on implementing it. > Once this is implemented I'll remove these fields from [1] if onionoo > includes these fields. It would be interesting to see how many relays currently have bitcoin/zcash or similar addresses in their ContactInfo fields. > While I agree that it would be nicer to have this as separate fields - > and this is the way to go on the long run (if anyone implements it) - in > practice this requires a lot more than people just changing their > ContactInfo string according to a specification: > - proposal(s) > - deployment of new tor version on the network > - tor code change (implementation) > - onionoo code change to parse new data > - atlas code change to display new data This is true. > Using ContactInfo does not require any tor/onionoo code change even > atlas is optional and relay operators don't have to wait for a new tor > version that supports it. They can basically start using it once the > specification for the format is done (<1month). Perhaps then we can use the fields that people choose to use as an indicator of which ones we should progress to proposals for changes to the descriptors. I would suggest though that if these do catch on, perhaps proposing an AdditionalInfo field as a catch-all field to house future properties until they can be formalised to avoid doing too much with the ContactInfo field? Thanks, Iain. signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Using ContactInfo to publish additional relay properties in a standardized way (opt-in)
Iain R. Learmonth: > The ContactInfo field doesn't need to be overloaded again. ): > > See proposal 234 [0] for adding bitcoin/zcash/etc addresses. Thank you for the pointer. This proposal is from 2014 and I havn't found any trac ticket for it, so I guess no one is working on implementing it. Once this is implemented I'll remove these fields from [1] if onionoo includes these fields. > Maybe we can work out new fields for extrainfo documents [1] that could > contain some of this information. While I agree that it would be nicer to have this as separate fields - and this is the way to go on the long run (if anyone implements it) - in practice this requires a lot more than people just changing their ContactInfo string according to a specification: - proposal(s) - deployment of new tor version on the network - tor code change (implementation) - onionoo code change to parse new data - atlas code change to display new data Using ContactInfo does not require any tor/onionoo code change even atlas is optional and relay operators don't have to wait for a new tor version that supports it. They can basically start using it once the specification for the format is done (<1month). I see you played with a long (>5k) contact string already ;) https://atlas.torproject.org/#details/A5B70A588FC01FAC572536B0BC35C7DD4252842A [1] https://github.com/nusenu/ContactInfo-Information-Shareing-Specification -- https://mastodon.social/@nusenu twitter: @nusenu_ signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Using ContactInfo to publish additional relay properties in a standardized way (opt-in)
> ExtraInfo documents are also one possibility for communicating > OutboundBindAddress values, as well. While publising OBA's may be wanted by censoring firewall pedants, it's not productive for relay operators who wish, as is their right, to offer tor users the chance to use exit IP's that are *not* listed in the consensus for easy scraping by such pedants, such that users might have more of a chance to participate freely reading materials on the internet, communicating on forums etc, where such pedants have otherwise blocked access. Operators that OBA, NAT, VPN, or provide VPN termination IP's on their nodes, have my support as they offering additional censorship resistant services of that kind, even if only marginal due to exit testing, it's still benefit against lazy censors. Other than that, many times suggested has been ways for relays and primarily third parties subscribable services to calculate, denote, and promulgate for user consumption various "extra" properties of relays, such as Web of Trust (WoT), diversity, other metrics. If not in "Contact", a second, community defined and wikified field could be adopted. Or made purely third party lookup subscription or patch if all such other is refused in tor directly. Thanks Nusenu, and for all your various work. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Using ContactInfo to publish additional relay properties in a standardized way (opt-in)
"Iain R. Learmonth" wrote: > Hi, > > On 14/10/17 23:01, nusenu wrote a proposal. > > The ContactInfo field doesn't need to be overloaded again. ): > > See proposal 234 [0] for adding bitcoin/zcash/etc addresses. > > Maybe we can work out new fields for extrainfo documents [1] that could > contain some of this information. ExtraInfo documents are also one possibility for communicating OutboundBindAddress values, as well. > > I do think this is a useful thing to look at, but I just don't think > that ContactInfo is the right way to go about it. I concur. > > [0]: > https://gitweb.torproject.org/torspec.git/tree/proposals/234-remittance-addresses.txt > [1]: https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n799 > Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * ** * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * *-- Gov. John Hancock, New York Journal, 28 January 1790 * ** ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Using ContactInfo to publish additional relay properties in a standardized way (opt-in)
Hi, On 14/10/17 23:01, nusenu wrote a proposal. The ContactInfo field doesn't need to be overloaded again. ): See proposal 234 [0] for adding bitcoin/zcash/etc addresses. Maybe we can work out new fields for extrainfo documents [1] that could contain some of this information. I do think this is a useful thing to look at, but I just don't think that ContactInfo is the right way to go about it. [0]: https://gitweb.torproject.org/torspec.git/tree/proposals/234-remittance-addresses.txt [1]: https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n799 Thanks, Iain. signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
