-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Created a filesystem abstraction around IDA's netnode API to allow interacting with large files in the database. #70
Open
arizvisa
wants to merge
13
commits into
master
Choose a base branch
from
GH-8
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
…stem index with support for a dirty cache to do partial updates.
… an exception if the user tries to add a non-unique name.
… and fixed the way free-blocks were determined.
… entries that cross over a sector boundary.
…allow reusing of blocks until they're completely empty.
…mmit()` as the semantics of the new name are more accurate.
… index class, and cleaned up their verbiage a bit.
…d documented most of its methods.
…so that the name (which should change less) is followed by the content.
…__repr__()` method.
…he "content" field is a list.
…le so that it only contains sizes and the allocation table.
…ssistance with keeping track of interval overlap.
arizvisa
force-pushed
the
master
branch
7 times, most recently
from
February 10, 2021 10:09
5018d79
to
4f457a4
Compare
arizvisa
force-pushed
the
master
branch
2 times, most recently
from
May 27, 2022 23:47
4bdeba3
to
6ebd6fe
Compare
arizvisa
force-pushed
the
master
branch
2 times, most recently
from
August 22, 2022 20:05
7534294
to
cd3c2fd
Compare
arizvisa
force-pushed
the
master
branch
2 times, most recently
from
February 22, 2023 23:37
bc78896
to
b6bfcab
Compare
arizvisa
force-pushed
the
master
branch
2 times, most recently
from
December 3, 2023 05:45
6872422
to
af07f16
Compare
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 wraps the IDAPython netnode API (supvals, and blobs) in order to allow the storage of arbitrarily-named and arbitrarily-sized files in a database. This is done using two types of netnodes. The
$ filesystem.index
netnode contains the directory index which is flat and is treated pretty much like a keystore, and then the$ filesystem.contents
netnode which is responsible for containing the actual contents of the files described in the directory index.Normally one could use the netnode API and simply store their contents in a blob, but due to the way IDAPython exposes this API the entire contents of the blob needs to be completely loaded into memory when reading or writing. The filesystem abstraction implemented by this PR thus allows a user to storage arbitrarily-large files and read them as an i/o stream instead of having to load the entire contents of the file in memory.
This feature was suggested in issue #8 and aims to close it.