Verify Google Lens OCR downloads before unpack - #35
Draft
Blackspirits wants to merge 2 commits into
Draft
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.
Summary
The Google Lens OCR standalone downloader fetches pinned Windows/Linux release archives that are unpacked immediately by the OCR installer, but the downloaded bytes were not authenticated.
This change:
Validation
timminator/Chrome-Lens-OCRv3.4.0Base is current upstream
c38daaf93ff5b36e361619e7e336afc4b52b80c0.AI assistance: ChatGPT was used to audit the Google Lens OCR download/unpack path, verify the official GitHub release digests, implement integrity checks, and add regression coverage.