This repository has been archived by the owner on Dec 19, 2024. It is now read-only.

Investigate caching Rekall sessions #332

Open

brifordwylie opened this issue Aug 5, 2014 · 1 comment

Assignees

Labels

feature performance

Milestone

Member

brifordwylie commented Aug 5, 2014

In theory we should be able to serialize the Rekall session and put in in the data store for reuse if we encounter the same md5 memory image.

brifordwylie self-assigned this

brifordwylie added feature labels

Member Author

brifordwylie commented Aug 6, 2014

The state of Rekall session serialization is extremely alpha right now :)

So going to table this for a bit... (moving to 0.5)

brifordwylie added on_deck and removed in_progress labels

brifordwylie removed the on_deck label

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.