You did this with an AI and you do not understand what you're doing here
1–10 of 571 posts
Re: You did this with an AI and you do not understand what you're doing here
#2Jump to the point: https://hackerone.com/reports/3340109#:~:text=you%20did%20th...
Re: You did this with an AI and you do not understand what you're doing here
#3Jump to the point: https://hackerone.com/reports/3340109#:~:text=you%20did%20th...
[deleted]
Re: You did this with an AI and you do not understand what you're doing here
#4There must be other corporate bounty programs they could DDOS with fake reports - doing it to curl surely won't yield much profit.
Re: You did this with an AI and you do not understand what you're doing here
#5Resume hit piece, .
What an absolute shamble of an industry we have ended up with.
Re: You did this with an AI and you do not understand what you're doing here
#6I wonder where the balance of “Actual time saved for me” vs “Everyone else's time wasted” lies in this technological “revolution”.
Re: You did this with an AI and you do not understand what you're doing here
#7These are the people that I imagine who go on forums and threads to announce how great AI is and are unable to provide any critique. They are blinded by ignorance.
Re: You did this with an AI and you do not understand what you're doing here
#8There must be other corporate bounty programs they could DDOS with fake reports - doing it to curl surely won't yield much profit.
This is headline driven development. Sooner or later one of these reports will make it and there will be much rejoicing.
Re: You did this with an AI and you do not understand what you're doing here
#9This must be _absolutely exhausting_.
Re: You did this with an AI and you do not understand what you're doing here
#10Crazy how he doubled down by just pasting badger's answer into Chat and submitting the (hilariously obvious AI) reply:
> Thanks for the quick review. You’re right — my attached PoC does not exercise libcurl and therefore does not demonstrate a cURL bug. I retract the cookie overflow claim and apologize for the noise. Please close this report as invalid. If helpful, I can follow up separately with a minimal C reproducer that actually drives libcurl’s cookie parser (e.g., via an HTTP response with oversized Set-Cookie or using CURLOPT_COOKIELIST) and reference the exact function/line in lib/cookie.c should I find an issue.