chore(deps): update ghcr.io/alam00000/bentopdf docker tag to v2.8.7 - #705
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update ghcr.io/alam00000/bentopdf docker tag to v2.8.7#705renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.8.6→2.8.7Release Notes
alam00000/bentopdf (ghcr.io/alam00000/bentopdf)
v2.8.7: CVE Fixes - v2.8.7Compare Source
With thanks to @thefoulowl, @alhamrizvi-cloud, and @de3erve-hunter for responsibly disclosing these. ❤️
A note from the maintainer
I genuinely appreciate people taking the time to look into BentoPDF's security with thoughtful reports that make the project better, and improve the project's security.
But having said that, there has been a big problem. Since LLMs became widely available, a large share of incoming security reports are low effort, machine generated submissions describing, at best, minor bugs, not vulnerabilities, and certainly not CVEs. In one such instance, I received over twenty such "CVE" reports from three different accounts within about thirty minutes which is of course not humanly possible to write with detail in such a short stretch. But none of which held up, and all of which were clearly LLM generated. Reviewing each of them carefully still took me a week
I'm not against using AI to assist research; used judiciously, it's a great tool. But I won't spend time reviewing reports or even PRs whose authors haven't first read the actual code, tested against
main, and confirmed the issue is real. If you file a report, please make sure you've done at least that. Genuine, verified findings will always be welcomed and credited.Also Coming next in next release!
The next release of BentoPDF will be the biggest one yet:
Kura will also be available via CLI or in the browser (via WASM)
With this shipped, I'll also have more time to review code and PRs actively again.
What's Changed
New Contributors
Full Changelog: alam00000/bentopdf@v2.8.6...v2.8.7
v2.8.7: CVE Fixes - v2.8.7Compare Source
With thanks to @thefoulowl, @alhamrizvi-cloud, and @de3erve-hunter for responsibly disclosing these. ❤️
A note from the maintainer
I genuinely appreciate people taking the time to look into BentoPDF's security with thoughtful reports that make the project better, and improve the project's security.
But having said that, there has been a big problem. Since LLMs became widely available, a large share of incoming security reports are low effort, machine generated submissions describing, at best, minor bugs, not vulnerabilities, and certainly not CVEs. In one such instance, I received over twenty such "CVE" reports from three different accounts within about thirty minutes which is of course not humanly possible to write with detail in such a short stretch. But none of which held up, and all of which were clearly LLM generated. Reviewing each of them carefully still took me a week
I'm not against using AI to assist research; used judiciously, it's a great tool. But I won't spend time reviewing reports or even PRs whose authors haven't first read the actual code, tested against
main, and confirmed the issue is real. If you file a report, please make sure you've done at least that. Genuine, verified findings will always be welcomed and credited.Also Coming next in next release!
The next release of BentoPDF will be the biggest one yet:
Kura will also be available via CLI or in the browser (via WASM)
With this shipped, I'll also have more time to review code and PRs actively again.
What's Changed
New Contributors
Full Changelog: alam00000/bentopdf@v2.8.6...v2.8.7
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.