db_info: populate md5/sha256 (#1 residual) - #10
Merged
Merged
Conversation
The host now carries executable md5/sha256 in the OpenProgram response (0xeb/libghidra). Map them into the db_info row; the columns and ProgramInfoRow fields already existed but were never filled. Completes the #1 db_info metadata.
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.
Fills the long-empty
db_info.md5/sha256columns by mapping them from the opened program's metadata, now that the host carries them (0xeb/libghidra#17).The SQL columns and
ProgramInfoRowfields already existed; only the value wiring was missing. With the #1 db_info fix already merged (active program is opened in headless), this flows in headless and--urlalike.Depends on 0xeb/libghidra#17 (merge that first). Verified:
/bin/lsdb_info md5985bea2a…+ sha256.