This is stupid. You’re still “connecting directly” to the instance. Your concern is about logging and traffic from your ISP being logged. This is the dumbest way to achieve this though, and reads as overly paranoid.
Just because you’re hanging one side out on Tor, does not mean your traffic isn’t logged. I don’t want to devolve into basic network operations, but this is stupid.
If I understand this correctly, you’re still forwarding it a port from one network to another. It’s just in this case, instead of a port on the internet, it’s a port on the TOR network. Which is still just as open, but also a massive calling card for anyone trolling around the TOR network to things to hack.
Which is still just as open, but also a massive calling card for anyone trolling around the TOR network
Luckily, it is no longer possible to easily sniff the new v3 addresses by deploying a malicious relay. Any attack to even reveal the existence of a hidden service would require a very specialized setup. And we’re just talking discovery, not the ability to connect and attack the actual service running there.
Isn’t it super slow to access via Tor?
lol I would open every port on my router and route them all to wireguard before I would ever consider doing this
