-
```
It's a Windows 7 image where I forgot to put the profile:
$ python vol.py -f win7vss.vmem hivelist
Volatile Systems Volatility Framework 1.4_rc1
Virtual Physical Name
Traceback (most recen…
-
```
What steps will reproduce the problem?
1. svn update to latest trunk (latest malware.py, too)
2. run apihooks module
imageinfo:
Suggested Profile(s) : WinXPSP3x86, WinXPSP2x86 (Instanti…
-
```
I just let vadinfo run across all the processes and it blew up with this
backtrace:
Traceback (most recent call last):
File "vol.py", line 185, in
main()
File "vol.py", line 176, in mai…
-
```
I took a crack at fixing kpcrscan for x64. Here's a patch that solves some of
the potential issues, but it still doesn't work.
The patch is built on r1289 from trunk.
```
Original issue rep…
-
```
So currently the DTB is searched like this (basic.py):
1. Each profile has a magic signature which seems to be different for different
releases, but ends up pointing at the start of an _EPROCESS.…
-
```
So upon investigating a new plugin that has to traverse a *lot* of registry
keys. In so doing, it calls is_valid_address often which calls
HiveAddressSpace vtop, which calls the following:
sel…
-
```
So upon investigating a new plugin that has to traverse a *lot* of registry
keys. In so doing, it calls is_valid_address often which calls
HiveAddressSpace vtop, which calls the following:
sel…
-
```
So currently the DTB is searched like this (basic.py):
1. Each profile has a magic signature which seems to be different for different
releases, but ends up pointing at the start of an _EPROCESS.…
-
```
This bug is probably the result of ambiguous validity checking. I did a vadinfo
on the image xp-laptop-2005-06-25.img and I could see lines like:
FileObject @823c234c FileBuffer @ f000af7e …
-
```
This bug is probably the result of ambiguous validity checking. I did a vadinfo
on the image xp-laptop-2005-06-25.img and I could see lines like:
FileObject @823c234c FileBuffer @ f000af7e …