| ▲ | cryptonector 4 hours ago | ||||||||||||||||||||||
Idk that u/notmine1337 meant that. I have questions: - why was this not a secure vulnerability report, why was it public? - why was this closed [by the submitter]? For the second question, I suspect it's because they were told a different fix was coming. | |||||||||||||||||||||||
| ▲ | jakewins 3 hours ago | parent | next [-] | ||||||||||||||||||||||
Why it was closed, surely, was because the only reaction to the PR was a bot saying it will automatically close the PR soon because of inactivity? I know I have opened a lot of PRs where the only result is I get bot spam in my email and no project reaction, so I close the PR to stop the bot spam; if nobody from Oracle has reacted in 2 months it seems unlikely anyone will. Nowadays I’ve stopped opening “cold-call” PRs like this. I find a way to chat with a maintainer first and anchor what I want to do (“I hit this bug, would you take a PR to fix it? I was thinking it could be solved by x, would that work?” Much much better outcomes that way. | |||||||||||||||||||||||
| |||||||||||||||||||||||
| ▲ | philipwhiuk 3 hours ago | parent | prev [-] | ||||||||||||||||||||||
> why was this not a secure vulnerability report, why was it public? Because it was seen as a crash not an RCE. AI's power has been chaining simple crashes into exploits. But that's not generally going to be true. | |||||||||||||||||||||||
| |||||||||||||||||||||||