Stream acquisitions to zip archives#110
Merged
Merged
Conversation
# Conflicts: # acquisition/acquisition.go # main.go
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
1 participant
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
This changes androidqf so every acquisition is written through the streaming zip path. When
key.txtis present, the zip stream is age-encrypted as<UUID>.zip.age; when no key is available, androidqf writes an unencrypted<UUID>.zipinstead of building an acquisition folder.The change removes the old folder-output and post-processing compression/encryption path, so modules write through one shared archive writer.
APK acquisition now preserves unique archive names for split APKs, raises the in-memory pull limit to 500 MiB, and handles oversized APKs without dropping them. Unencrypted oversized APKs are spooled to a temporary file for certificate checks before being archived; encrypted oversized APKs are streamed directly into the archive and record that certificate verification was skipped because they exceeded the streaming buffer limit.
Trusted-certificate filtering is applied consistently for encrypted and unencrypted archives whenever the APK fits within the streaming buffer, so trusted APKs are removed when the user chooses that option.
Closes #20