If you include this in the image, then your machine can talk to .onion addresses natively across the system, without having to use torify or socks5 proxy setups. This enables in doing things like sending logs to *.onion , having an OOB at a different .onion , and more.<p>I send my IoT traffic to a MQTT onionseerver I run.<p><a href="https://cdn.hackaday.io/files/12985555550240/Linux%20DNS%20Resolver%20for%20Onions.txt" rel="nofollow">https://cdn.hackaday.io/files/12985555550240/Linux%20DNS%20R...</a>
Great documentation!<p>I particularly like that you mentioned "NAT Traversal" as one of the benefits of hidden services.<p>I think that's an overlooked feature that would in many cases be enough of a reason for one to use them, even without caring for the added privacy.
If all you need is a Go library for connecting to a Tor daemon and adding/removing hidden services: <a href="https://godoc.org/github.com/wybiral/torgo" rel="nofollow">https://godoc.org/github.com/wybiral/torgo</a>
Good stuff! I wish there was some good in-depth and well explained article on how to write or hook up your own controller. I mean, there is the official doc for this but it's not really a hands-on IMHO.