What’s your go too (secure) method for casting over the internet with a Jellyfin server.

I’m wondering what to use and I’m pretty beginner at this

  • Novi@sh.itjust.worksEnglish
    394·
    10 hours ago

    I would not publicly expose ssh. Your home IP will get scanned all the time and external machines will try to connect to your ssh port.

    • Lucy :3@feddit.orgEnglish
      34·
      10 hours ago

      fail2ban with endlessh and abuseipdb as actions

      Anything that’s not specifically my username or git gets instantly blocked. Same with correct users but trying to use passwords or failing authentication in any way.

      • mosiacmango@lemm.eeEnglish
        9·
        3 hours ago

        Youve minimized login risk, but not any 0 days or newly discovered vulnerabilites in your ssh server software. Its still best to not directly expose any ports you dont need to regularly interact with to the internet.

        Also, Look into crowdsec as a fail2ban replacement. Its uses automatically crowdsourced info to pre block IPs. A bit more proactive compared to abuseipdb manual reporting.

    • drkt@scribe.disroot.orgEnglish
      123·
      9 hours ago

      They can try all they like, man. They’re not gonna guess a username, key and password.

        • drkt@scribe.disroot.orgEnglish
          81·
          6 hours ago

          If you’re going to open something, SSH is far, far more battle-tested than much other software, even popular software. Pragmatically, If someone is sitting on a 0-day for SSH, do you genuinely think they’re gonna waste that on you and me? Either they’re gonna sell it to cash out as fast as possible, or they’ll sit on it while plotting an attack against someone who has real money. It is an unhealthy level of paranoia to suggest that SSH is not secure, or that it’s less secure than the hundreds of other solutions to this problem.

          Here is my IP address, make me eat my words.
          2a05:f6c7:8321::164 | 89.160.150.164

          • pm_me_your_puppies@infosec.pubEnglish
            3·
            5 hours ago

            You got balls to post you public addresses like that… I mean I agree with you wholeheartedly and I also have SSH port forwarded on my firewall, but posting your public IP is next-level confidence.

            Respect.

          • Ptsf@lemmy.worldEnglish
            51·
            6 hours ago

            I linked a relevant vulnerability, but even ignoring that, pragmatically, you feel they’d be targeting specific targets instead of just what they currently do? (That, by the way, is automating the compromise of vulnerable clients in mass scale to power botnets). Any service you open on your device to the internet is inherently risky. Ssh best practices are, and have been since the early days, not to expose it to the internet directly.