• 5 Posts
  • 204 Comments
Joined 15 days ago
cake
Cake day: January 6th, 2026

help-circle


  • One way to go about the network security aspect:

    Make a separate LAN(optionally: VLAN) for your internals of hosted services. Separate from the one you use to access internet and use with your main computer. At start this LAN will probably only have two machines (three if you bring the NAS into the picture separately from JF)

    • The server running Jellyfin. Not connected to your main network or internet.

    • A “bastion host” which has at least two network interfaces: One connected outwards and one inwards. This is not a router (no IP forwarding) and should be separate from your main router. This is the bridge. Here you can run (optional) VPN gateway, SSH server. And also an HTTP reverse proxy to expose Jellyfin to outside world. If you have things on the inside that need to reach out (like package updates) you can have an HTTP forward proxy for that.

    When it’s just two machines you can connect them directly with LAN cable, when you have more you add a cheap network switch.

    If you don’t have enough hardware to split machines up like this you can do similar things with VMs on one box but that’s a lot of extra complexity for beginners and you probably have enough of new things to familiarize yourself with as it is. Separating physically instead of virtually is a lot simpler to understand and also more secure.

    I recommend firewalld for system firewall.







  • I think it depends a lot on what you are building.

    For bigger projects and apps leveraging the mobile platform I’m 100% with you.

    These kinds of frameworks can still be a good fit for a quick MVP demo, as a stepping stone for porting an existing web app, or if all you really want is a glorified web view (or are PWAs enough for the last one these days?)

    Specifically RN is in terrible shape and IMO something to avoid though.



  • Tricking users into using Snap without realizing it, making them unknowingly vulnerable to exploits like this, would be really really bad and unethical on Canonical’s part.

    That is not what is happening at all.

    Just so nobody is confused or gets afraid of their install: Getting the Firefox snap installed via Ubuntus apt package does not make users vulnerable to what is talked about here and is just as safe as the apt package version. For Firefox snaps might even be safer since you will probably get security patches earlier than with apt upgrades and get some sandboxing. In both cases you are pulling signed binaries from Canonical servers.

    The post is about third-party fake snaps. If you run a snap install command from a random web site or LLM wkthout checking it, or making a typo, then you are at risk. If Ubuntu didnt have snaps, this would be malicious flatpaks. If Ubuntu didnt have flatpaks, it would be malicious PPAs. And so on. Whatever hosted resource gets widely popular and allows users to blindly run and install software from third-parties will be abused for malware, phishing, typosquatting and so on. This is not the fault of the host. You can have access to all the apps out there you may ever want or you can safely install all your apps from one trusted source. But it’s an illusion that you can never have both.

    People have opinions about if snaps are a good idea or not and thats fine but there shouldnt be FUD. If you are using Canonicals official snaps and are happy with them you dont have to switch.







  • kumi@feddit.onlinetoPrivacy@programming.devQuestion
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    3 days ago

    Digg is just a shallow VC play that acquired the name and brand I think. No actual relation to OG Digg AFAIK. At launch they had only closed Android and iOS apps, no web.

    OP: What makes you interested in thes and what’s your own take? BTW please try to put a more descriptive title for future posts!