when reading through the jellyfin with chromecast guide i realized that it would probably be less effort to just let the casting api be public, with the added bonus that i could then cast my library to any device that supports it. but that seems like it would paint a giant target on the server.

what’s the recommended way of doing stuff like this? ideally i want to be able to go to someone’s house and just play some of my media on their tv.

not that any of this is doable in the near future, since i’m behind cgnat and won’t get my colocated bounce server up until spring.

    • diegantobass@lemmy.worldEnglish
      0·
      9 days ago

      Quick question: If I look through the ssh log and I don’t see the hundred of attempts, what could be going on?..

      • teawrecks@sopuli.xyzEnglish
        0·
        9 days ago

        Are you not actually open to the public internet? Is it running on a nonstandard port? Is it already pwned and something is scrubbing logs?

        • diegantobass@lemmy.worldEnglish
          0·
          9 days ago

          Non standard port. But aren’t secret chinese hack farm scanning wider than just 22 ? I don’t know and deep down believe that it’s pawned and scrubbing logs.

          • teawrecks@sopuli.xyzEnglish
            1·
            8 days ago

            The resources required to port scan every port on every IP is generally not worth it. AFAIK they tend to stick to lower ports or popular ports. Unless they’re intentionally targeting a specific IP or IP range, they’re just looking for low hanging fruit.

      • GreenCrunch@piefed.blahaj.zoneEnglish
        0·
        9 days ago

        I am not sure lol. perhaps your ssh port isn’t exposed to the internet, or maybe the bots are just ignoring you? maybe your hosting provider has some sort of security process to reject those attempts preemptively?

        I have no clue