Comment on What's the security situation when opening a jellyfin server up for casting?

• diegantobass@lemmy.world ⁨4⁩ ⁨weeks⁩ ago

  Aren’t zero day very specific? Or maybe it’s become a very generic term.

  Anyway, I am under the impression that either it’s suddenly very simple to hack into EVERYONE because someone zero dayed the wireguard protocol and there a major flow in it, it’s a shitshow, for all, for some, just me or nobody, whatever. Or it’s a very targeted attack on me personaly, and that’s a whole other story and the means to protect my pictures of my cats and my cool public domain movies collection are different (think social engineering). Also port 22 being bombarded by brute force attempts so don’t choose a password that’s 6 letters thanks.

  I KNOW I am missing many things, but still, I don’t get it.

  source

  • GraveyardOrbit@lemmy.zip ⁨4⁩ ⁨weeks⁩ ago

    [deleted]

    source

    • diegantobass@lemmy.world ⁨4⁩ ⁨weeks⁩ ago

      React2Shell is exactly the shitshow situation yes. Suddenly we are all at risk. But in this case, I’m sorry to say that my cats’ pictures are worthless.

      Your point on nginx/wireguard makes me think that it might be better to htaccess through a reverse proxy than relying on a built in login system. For exemple, I should deactivate jellyfin’s login and put it behind an htaccess at the proxy’s level. Is that completely dumb?

      Anyway, I clearly need to research “threat models” and cyber/infosec more. Thank you very much!

      source