cURL stopped HackerOne bug bounty program due to excessive slop reports
github.comExact messaging is:
> We have concluded the hard way that a bug bounty gives people too strong incentives to find and make up "problems" in bad faith that cause overload and abuse.
Anyone who follows Daniel Stenberg on social media, or his talks, or his blog, or cURL’s HackerOne, know the struggle AI slop reports have been on the cURL project, and how they’ve tried to work with HackerOne to reduce those and have been talking for months about terminating it for that very reason.
As could be expected, curl was the first one, but now the prediction is in the air about whether slop will kill also bug bounties themselves, and maybe even GitHub; cf.
Slop bug bounty reports have always been an issue. Sites like HackerOne have a triage team that's supposed to filter through the garbage, before it gets to program management.
On the other side of it, I've submitted reports that are valid, have the steps, and show impact. Companies will do everything in their power to not pay you, including changing the back-end code or just stating it doesn't have any impact on business.
> Sites like HackerOne have a triage team that's supposed to filter through the garbage, before it gets to program management.
Daniel Stenberg, leader and BDFL of the cURL project, has been in contact with HackerOne for at least several months to resolve the situation. It was fruitless. Daniel’s social media posts and blog make that clear.
> Companies will do everything in their power to not pay you, including changing the back-end code or just stating it doesn't have any impact on business.
That doesn’t apply to cURL at all.