Record ADB host public key in acquisition archives - #120
Merged
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
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.
Each acquisition now records the public half of the ADB host key as
adb_host_key.puband inacquisition.json. This allows analysts to compare an acquisition with ADB authorization records without placing the private host key in collected evidence.AndroidQF reads the normal per-user public-key sidecar and, when it is missing, asks ADB to derive the public key from the private key. Failure to capture this supplemental metadata is reported as a warning and does not prevent collection.
The documentation clarifies that the key identifies the ADB host identity rather than a specific client program, because AndroidQF and other ADB tools normally share the same per-user key.