Fix: cache path for python of Microsoft Store
version.
#805
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.
Description
Hello, everyone in the community! 🙂
I found something interesting while working on the symbol cache path in a
Windows
environment.We are using cache so that
volatility3
can quickly find information aboutSymbol
.And it is usually stored according to the path stored in the
constants
.We can see through the log that we use the cache file. (using
-vvvv
)However, I could not find the
data_*.cache
file that the log points to in the local storage.As a result of this investigation, the folder where the
data_*.cache
was stored was located elsewhere.Nevertheless, there was no problem with the operation of
volatility3
.Solution
A detailed study of this phenomenon confirmed that the
Microsoft Store
version ofPython
treatsWindows
internal folders differently for their access and use. (like symbolic link)Therefore, there was no problem with using it, but the log informed me of other folders and files.
I have patched this so that other contributors and users do not experience confusion in their work.
This was also present in
Python
's official documents, and I borrowed a solution.Result