• 0 Posts
  • 16 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
rss


  • Yeah, it’s true, a lot of things suck. They can and do get better though. I have a partner with BPD. They’ve been through a LOT of rough times, but they’re now very loved and they enjoy their current job and have plenty of friends who care about and support them.

    Therapy helps and sometimes, the world isn’t always an absolute dick to everyone forever. Life changes and the world revolves and people find each other.

    I hope you find your people too and a place where you can feel a little less shitty. :)

    Edit: if you’re feeling THAT shitty maybe consider reaching out to your local suicide hotline? People like that can help.



  • How about pseudonymous as a compromise? Votes could be publicly federated but tied to some uuid instead of the username. That way you still have the same anti spam ability (can see that a user upvoted these things from this instance at this time) but can’t tie it directly to comments or actual user accounts without some extra osint.

    It might be theoretically possible to correlate the uuids with an account’s activity and dox the user in some cases, especially with some instances having a single user, but it would be very difficult or impossible to do on larger instances and would add an extra layer. Single user instances would be kind of impossible to make totally private anyway because they can be identified by instance.





  • Best is very subjective.

    .world is a good general purpose instance for just about anything. I think it has the biggest population at the moment, so communities there are likely to get at least some engagement.

    For “general discussion” it doesn’t really matter. The instances are federated so you’ll likely get general discussion in comments from lots of people from lots of instances anyway, wherever your community is based.

    Some people get almost nationalistic about their chosen instances or have grudges against people from certain other instances. There’s sometimes inter-instance politics with some servers defederating with others or threatening to for various reasons. It’s kinda fun to watch in a popcorn drama kind of way. For the most part, the instance doesn’t matter.



  • They’re not files, it’s just leaking other people’s conversations through a history bug. Accidentally putting person A’s “can you help me write my research paper/IT ticket/script” conversation into person B’s chat history.

    Super shitty but not an uncommon kind of bug. Often either a nasty caching issue or screwing up identities for people sharing IPs or similar.

    It’s bad but it’s “some programmer makes understandable mistake” bad not “evil company steals private information without consent and sends it to others for profit” kind of bad.



  • Tailscale isn’t an exposed service. Headscale is

    Absolutely! And it’s a great system that I thoroughly recommend. The attack surface is very small but not non-existent. There have been RCE using things like DNS rebinding(CVE-2022-41924) etc. in the past and, although I’m not suggesting that it’s in any way vulnerable to that kind of thing now, or that it even affected most users we don’t know what will happen in future. Trusting a single point of failure with no defence in depth is not ideal.

    it’s more work and may not always be worth the effort

    I don’t really buy this. Certs have been free and easy to deploy for a long time now. It’s not much more effort than setting up whatever service you want to run as well as head/tailscale, and whatever other fun services you’re running. Especially when stuff like caddy exists.

    I recommended SmallStep+Caddy.

    Yes! Do this if you don’t want to get your certs signed for some reason. I’m only advocating against not using certs at all.

    Are you suggesting that these attack techniques are effective against zero trust tunnels

    No I’m talking about defence in depth. If Tailscale is compromised (or totally bypassed by someone war driving your WiFi or something) then all those services are free to be impersonated by a threat actor pivoting into the local network after an initial compromise. Don’t assume that something is perfectly safe just because it’s airgapped, let alone available via tunnel.

    I feel like it’s a bit like leaving all your doors unlocked because there’s a big padlock on the fence. If someone has a way to jump the fence or break the lock you don’t want them to have free reign after that point.


  • there’s an argument that HTTPS isn’t really required…

    Talescale is awesome but you gotta remember that Talescale itself is one of those services (Yikes). Like all applications it’s potentially susceptible to vulnerabilities and exploits so don’t fall into the trap of thinking that anything in your private network is safe because it’s only available through the VPN. “Defence in depth” is a thing and you have nothing to lose from treating your services as though they were public and having multiple layers of security.

    The other thing to keep in mind is that HTTPS is not just about encryption/confidentiality but also about authenticity/integrity/non-repudiation. A cert tells you that you are actually connecting to the service that you think you are and it’s not being impersonated by a man in the middle/DNS hijack/ARP poison, etc.

    If you’re going to the effort of hosting your own services anyway, might as well go to the effort of securing them too.