Also at @me@social.k3can.us on Mastodon. Blog is at blog.k3can.us

  • 4 Posts
  • 108 Comments
Joined 3 years ago
cake
Cake day: June 21st, 2023

help-circle
  • Oh, maybe I misunderstood? It sounded like he didn’t understand what advantage a “tunnel” could provide.

    If your server is behind CGNAT, you need a TURN-style “tunnel” to allow incoming connections. If you have your own remote server with a public IP, then you can absolutely use that and create the tunnel using wireguard (or openvpn, ssh, etc).

    I just mentioned CF in my blog post because it’s probably the most popular solution.

    The point is, if you have CGNAT, you need to create that “tunnel” somehow if you want to allow incoming connections.






  • Sorry, I think I misread the comment when I made my initial reply.

    Edit:

    If you mean the key provided for the demonstration, you could ensure that you get the correct one by checking the signature (it’s signed by my personal key) or by doing the initial download through i2p or tor. Once it’s added to your keyring, you maintain that same key for all the subsequent checks. Or, if you don’t want to do either, you could consider it as a Trust-on-first-use system.

    The important point is that it’s a layered system, rather than a single point of trust, and that once you trust it, it cannot be compromised.




  • Not directly, but I believe mTLS would break if the traffic was intercepted/altered, so it sort of works to test the connection.

    mTLS requires installing a certificate on the client device, though. If you’re able to do that, then you’re also able to pin the correct cert or install a custom CA. This would be the “enterprise” solution, as far as I know, but doesn’t work well for public sites, since you can’t always configure your end-users devices.

    Edit: mTLS is still very useful, though. I use it to secure some of my services. It just doesn’t solve this specific problem.








  • Crowdsec does it by using crowd-sourced blocklists (hence the name). So if an IP triggers a scenario on other machines, that malicious address will be proactively added to your blocklist before it ever gets a chance to impact your machine.

    That is the big advantage of crowdsec over reactive-only solutions, like fail2ban.