• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: August 11th, 2025

help-circle




  • The problem is not the difficulties of any of these… if you are reasonably skilled you’ll master any of them… given enough time.

    When I was a student I maintained a Slackware up/running/updated for my gf at the time… was it hard? No but it was a gigantic waste of time… and what I learned is not comparable to the amount of wasted time.

    Same with OpenBSD… I love that operating system for networking (the most elegant firewall/netfilter I ever seen) but (1) didn’t have support for multi cpu for a looong time (2) drivers either worked out of box magically or good luck

    All people you mentioned have better things to do than babysit an operating system and Debian (fedora I don’t use for decade, can’t say) is a pretty reasonable compromise of not treating you like a kid and not making you waste time





  • You need static IP only if you want to host the autoritative DNS server for your domain (spoiler alert: you don’t).

    You don’t need to proxy your traffic via VPS (higher latency for no good reason) and the dyndns providers are over priced.

    What you need is:

    • Buy your domain
    • Use a free DNS provider (I used for years the excellent dns.he.net but it is a bit cumbersome. Nowadays I gave up and I now use cloudflare without any proxying, just pure DNS)
    • Point your registrar to the dns provider
    • use ddclient to update the IP of a domain entry (e.g. server.example.com)
    • add as many CNAME as you want that point to that entry (so you can have stuff like Jellyfin.example.com www.example.com Nextcloud.example.com)

    That’s all… ddclient will update that single dns entry every time your server restarts (or the IP lease expires and you get a new IP)

    The only thing you need to pay here is the domain (you can get free domains but that is another story and tbh I would not recommend, there are cheap domains out of there)




  • I haven’t looked in the tor protocol for more than a decade but if routing was done based on traditional networking parameters (ttl distance, ping, etc) pretty sure you would end up all your nodes in your jurisdiction.

    If you were using pure random, routing may involve only US (where there are a significant percentage of nodes)

    Instead you can see that rarely there are two nodes in the same jurisdiction.

    Years ago there were a config file mapping countries to jurisdictions and maybe that has been ditched but still I don’t buy that it is pure random or using traditional routing criteria


  • Of course not! For this reason you need different providers and jurisdictions for datacenters, operating systems, encryption providers.

    It’s the very same principle tor works: sure you can do traffic analysis and be able to “unmask” a tor user… and for this reason tor deliberately sends traffic across 3 different jurisdictions. Is it still possible to force 3 different nodes to cooperate for the unmasking? Sure… but you need 3 jurisdictions to collaborate with that.

    Also, fun fact: bank secrecy is still in effect for Swiss residents (regardless of the citizenship) and people resident outside of the US and EU. Because things are always more nuanced than they seem 🙂




  • The only safe phone is a phone with no data.

    Otherwise there will be tools to gain full access.

    Without forgetting the good old rubber hose attack

    FWIW I think the only way to keep confidential information is hosted in another country, encrypted, with no credentials (or even the name of the server) cached, all on open sources stacks, with the infrastructure provider different from the operating system provider different from the application provider and encryption provider

    Is this convenient? No Is this accessible to the average user? No

    I just think something at certain point went extremely wrong in history. We accepted control in exchange of convenience