Collection of potential security issues in Jellyfin · Issue #5415 · jellyfin/jellyfin
github.com
Collection of potential security issues in Jellyfin This is a non exhaustive list of potential security issues found in Jellyfin. Some of these might cause controversy. Some of these are design fla...

Collection of potential security issues in Jellyfin This is a non exhaustive list of potential security issues found in Jellyfin. Some of these might cause controversy. Some of these are design fla…

  • bizarroland
    10•8 days ago

    You can’t say that a solution is no security at all when it requires time and intelligence to bypass.

    It is at least 0.01 security.

    • @[email protected]
      6•8 days ago

      Effort or no, if an attacker can reasonably bypass it, it’s not secure. That’s why software gets security patches all the time, why encryption/hashing algorithms can fall out of favor, and why quantum computing can be pretty fucking scary.

        • @[email protected]English
          5•7 days ago

          You’re hiding behind literal definitions to avoid addressing the functional issue/implications.

          This is like when somebody says “no one believes that“ and the other person finds a tweet by one person that believes the thing. The claim isn’t that literally not one person does, it’s that it’s so unusual you may as well act as if nobody does.

          Surely you understand how people talk and basic vernacular?

          • bizarroland
            5•7 days ago

            Surely you understand how a stupid response to a silly statement like it is one of the sayings of all time can be appropriate in humorous situations, right?

            I understand that you did not find it funny, but I hope that you can understand that it was my intention to be funny, and therefore a serious response is disproportionate.