@themachine - eviltoast
  • 0 Posts
  • 62 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle
  • Just know that this is a step forward in the direction of making it technically possible to force people to usw the app.

    I disagree. There is nothing stopping that as it is. What this really does is remove one more level of control from the end user on their device.

    Ask yourself if you trust them to not try and profit from this.

    Im not sure what you are getting at here. Of course i don’t trust “them”. Nor do i trust any corp. It’s those reasons among others why i have completely removed google from my computing life and almost exclusively use open source software as well as self host functionally all network services.



  • In the scope of wireguard it’ll just be a matter of you building appropriate firewall rules.

    Since you want their internet traffic to go through you then i assime you’re effectively pushing a 0.0.0.0/0 route to your clients. You then need to add firewall rules on your server to block traffic to its local subnet and in the future allow traffic to only your jellyfin server.

    This is also pretty simple and nothing wrong with that setup.





  • themachine@lemmy.worldtoSelfhosted@lemmy.worldJourney into self-hosting
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    8 days ago

    You did not answer what VPN tech you are using.

    Without that knowledge i would recommend setting up tailscale and having your users use that. If you want to be fully self hosted you can also run Headscale as the control plane instead of relying on Tailscales own service.

    I recommend tailscale as it is very easy to grant a user privileges to ONLY use an endpoint as an exit node but also grant access to any other endpoints as needed (such as your future jellyfin server) via theor ACLs.







  • If you want simple you’ll have to manually decrypt each time it needs doing.

    If you want it to be “automatic” then your best bet is something network based. A “simple” would be to just have a script ssh’s somewhere, pulls the decryption key, and then decrypts the disks. There’s plenty of flaws with this though as while a threat actor couldn’t swipe a single encrypted disk they could just log in as root, get your script, and pull the decryption key themselves.

    The optimal solution would be to also encrypt the root partition but now you need to do network based decryption at boot which adds further complexity. I’ve previously used Clevis and Tang to do this.

    I personally don’tencrypt my server root and only encrypt my data disks. Then ssh in on a reboot or power event and manually decrypt. It is the simplest and most secure option.


  • They do not work well in already humid environments but in a hot and dry climate they do quite well. It absolutely does add to the humidity (obviously) but speaking from experience I’d rather have a evap cooler than not if my AC is out.

    The largest difference in utilizing one over AC is that they rely on airflow so you need to actually ventilate the area you are cooling as compared to AC where you want a sealed space.

    The main driver is power efficiency. Only thing they are doing is running a small water pump and a big fan.







  • I prefer restic for my backups. There’s nothing inherently wrong with just making a copy if that is sufficient for you though. Restic will create small point in time snapshots as compared to just a file copy so I’m the event that perhaps you made a mistake and accidentally deleted something from the “live” copy and managed to propagate that to your backup it is a nonissue as you could simply restore from a previous snapshot.

    These snapshots can also be compressed and deduplicated making them extremely space efficient.