• deafboy@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    4 months ago

    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.

    • ramielrowe@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      4 months ago

      Yea, I don’t think this is necessarily a horrible idea. It’s just that this doesn’t really provide any extra security, but even the first line of this blog is talking about security. This will absolutely provide privacy via pretty good traffic obfuscation, but you still need good security configuration of the exposed service.

      • deafboy@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        4 months ago

        you still need good security configuration of the exposed service.

        In a sense that security comes in layers, yes. But in practice, this setup will prevent 100% of bots scanning the internet for exposed services, and absolute majority of possible targeted attacks as well. It’s like using any other 3rd party VPN, except there’s not a central point for the traffic to flow through.

        From the attackers point of view, nothing is listening there.

        I’ve used a similar setup in the past to access a device behind a NAT (possibly multiple NATs) and a dynamic IPv4. Looking back, that ISP was a pure nightmare.