• 0 Posts
  • 26 Comments
Joined 2 years ago
cake
Cake day: July 23rd, 2023

help-circle


  • So when I ask Let’s Encrypt for a cert, I ask for *.int.teuto.icu instead of specifically jellyfin.int.teuto.icu, that way I can use the same cert for any internally running service. Mostly I use SSL on everything to make browsers complain less. There isn’t much security benefit on a local network. I suppose it makes harder to spoof on an external network, but I don’t think that’s a serious threat for a home net. I used to use home.lan for all of my services, but that has the drawback of redirecting to a search by default on most browsers. I have my tailscale exit node running on my router and it just works with SSL like anything else.


  • I use a central nginx container to redirect to all my other services using a wildcard let’s encrypt cert for my internal domain from acme.sh and I access it all externally using a tailscale exit node. The only publicly accessible service that I run is my Lemmy instance. That uses a cloudflare tunnel and is isolated in it’s own vlan.

    TBH I’m still not really happy having any externally accessible service at all. I know enough about security to know that I don’t know enough to secure against much anything. I’ve been thinking about moving the Lemmy instance to a vps so it can be someone else’s problem if something bad leaks out.









  • As a professional pilot. I don’t think there’s any future in single pilot ops. Realistically the only time you need two pilots in a modern airliner is when shit’s fucked sideways, which is exactly the time the single pilot in this situation needs to work. Normal ops are easy. You could automate that no problem, what is hard is automating whatever combination of failures and weather the engineers never thought of.

    Maybe in cargo, where the stakes are lower, it’ll happen. But in passenger ops, I think we’ll go from 2 pilots to no pilots before we go to one pilot.