3 ms·
Reading your comment I think you're a little confused about what this is. This is for Cloudflare customers. Before this you went across normal Tor and hit an e
by jgrahamc 8y ago
Reading your comment I think you're a little confused about what this is.
This is for Cloudflare customers. Before this you went across normal Tor and hit an exit node and then went across the Internet to connection the nearest Cloudflare PoP. After this you go to the onion being run by Cloudflare eliminating the exit node and the hop across the Internet.
If you already have an onion for your service then you are already not using Cloudflare.
- kodablah 8y agoNah, I get it and think it's good for Cloudflare customers over what happens today. My comment was a bit of scattershooting admittedly, so I can clarify this point. > If you already have an onion for your service then you are already not using Cloudflare. To clarify my point, what I mean is I might have "kodablahforum.com" running behind Cloudflare but I might, as a convenience for my users, offer my service behind an onion service unrelated to Cloudflare. I am saying, if the service offers that option, it can be seen as a bit more secure (if you don't mind the unwieldiness of the onion service address) to access that instead of the regular domain that hits Cloudflare via an exit and then routes all traffic through Cloudflare onion services. Again, in general, I agree this is a complete improvement for non-onion-service using Tor browser users of Cloudflare customer sites. And I think it's a good pattern for sites/hosts/CDNs to follow (i.e. onions as HTTP alt services) in the current absence of acceptably secure/decentralized DNS for onion services. But direct onion service access hosted by the endpoint is always preferred over a middleman if it is an option.