2 ms·

This is a weird argument. Basically condoning security through obscurity: If nobody reports the bug then we just pretend it doesn’t exist, right? There are man

This is a weird argument. Basically condoning security through obscurity: If nobody reports the bug then we just pretend it doesn’t exist, right? There are many groups searching for security vulnerabilities in popular open source software who deliberately do not disclose them. They do this to save them for their own use or even to sell them to bad actors. It’s starting to feel silly to demonize Google for doing security research at this point.

KingMob 1y ago
> It’s starting to feel silly to demonize Google for doing security research at this point. Aren't most people here demonizing Google for dedicating the resources to find bugs, but not to fix them?
- watwut 1y ago
  And not giving the maintainners reasonable amount of time to fix. This was triggered by recent change of policy on google side.
  - surajrmal 1y ago
    The timeline is industry standard at this point. The point is make sure folks take security more seriously. If you start deviating from the script, others will expect the same exceptions and it would lose that ability. Sometimes it's good to let something fail loudly to show this is a problem. If ffmpeg doesn't have enough maintainers, then they should fail and let downstream customers know so they have more pressure to contribute resources. Playing superman and trying to prevent them from seeing the problem will just lead to burn out.
    - Orygin 1y ago
      Is it industry standard to run automatic AI tools and spam the upstream with bug reports? To then expect the bugs to be fixed within a 90 days is a bit much. It's not some lone report of an important bug, it's AI spam that put forth security issues at a speed greater than they have resources to fix it.
      - kllrnohj 1y ago
        "AI tools" and "spam" are knee jerk reactions, not an accurate picture of the bug filed: https://issuetracker.google.com/issues/440183164?utm_source=the%20new%20stack&utm_medium=referral&utm_content=inline-mention&utm_campaign=tns%20platform https://issuetracker.google.com/issues/440183164?utm_source=... whether or not AI found it, clearly a human refined it and produced a very high quality bug report. There's no AI slop here. No spam.

KingMob 1y ago

> It’s starting to feel silly to demonize Google for doing security research at this point. Aren't most people here demonizing Google for dedicating the resources to find bugs, but not to fix them?

watwut 1y ago
And not giving the maintainners reasonable amount of time to fix. This was triggered by recent change of policy on google side.
- surajrmal 1y ago
  The timeline is industry standard at this point. The point is make sure folks take security more seriously. If you start deviating from the script, others will expect the same exceptions and it would lose that ability. Sometimes it's good to let something fail loudly to show this is a problem. If ffmpeg doesn't have enough maintainers, then they should fail and let downstream customers know so they have more pressure to contribute resources. Playing superman and trying to prevent them from seeing the problem will just lead to burn out.
  - Orygin 1y ago
    Is it industry standard to run automatic AI tools and spam the upstream with bug reports? To then expect the bugs to be fixed within a 90 days is a bit much. It's not some lone report of an important bug, it's AI spam that put forth security issues at a speed greater than they have resources to fix it.
    - kllrnohj 1y ago
      "AI tools" and "spam" are knee jerk reactions, not an accurate picture of the bug filed: https://issuetracker.google.com/issues/440183164?utm_source=the%20new%20stack&utm_medium=referral&utm_content=inline-mention&utm_campaign=tns%20platform https://issuetracker.google.com/issues/440183164?utm_source=... whether or not AI found it, clearly a human refined it and produced a very high quality bug report. There's no AI slop here. No spam.