• @Getting6409@lemm.eeEnglish
    0•11 months ago

    Yeah I don’t think anyone sane would disagree. That’s what forced the decision for me, to expose or not. I was not going to try talking anyone through VPN setup, so exposure + whatever hardening practice could be applied. I wouldn’t really advocate for this route, but I like hearing from others doing it because sometimes a useful bit of info or shared experience pops up. The folder path explanation is news to me; time to obfuscate the hell out of that.

    • Saik0English
      0•11 months ago

      Yeah I don’t think anyone sane would disagree.

      Exactly… But I get chastised for pointing the problem out. Called a shill because I care about security.

      I RUN JELLYFIN. I HAVE IT RUNNING. Others you recommend it to should be made aware of the risks that’s all I’m trying to point out.

      The folder path explanation is news to me; time to obfuscate the hell out of that.

      You can get around the MD5 issue (a bit) by obfuscating your path. Instead of /movies/title (year)/title.ext… make it /mnt/MHhzTiM57Fv4wWQmkmb4DLDwVKoB628KBQzhBHQjGQVtsjhwRrFNU2NtRGJ4dUpg/movies/title (year)/title.ext and you’ll probably be pretty damn immune to the problem as it stands now… But just blatantly telling people to use Jellyfin isn’t a good answer here without that background.