-
```
I saw the new 2008 profiles and decided to give them a quick run... found one
issue so far...
On 2008 sp1, 'connections' goes into an infinite loop and 'sockets' blows up
with this error:
C:\U…
-
```
I saw the new 2008 profiles and decided to give them a quick run... found one
issue so far...
On 2008 sp1, 'connections' goes into an infinite loop and 'sockets' blows up
with this error:
C:\U…
-
```
What steps will reproduce the problem?
C:\Users\dmk\volatility>python vol.py -f ..\win7sp1x64.dmp --profile=Win7SP1x64
connscan
Volatile Systems Volatility Framework 2.1_alpha
Offset(P) Local A…
-
```
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…
-
```
I have installed volatility2.4 python version on windows2008r2sp1 server.
I have copied crash dumps from one of windows server and am able to run
imagecopy, kdbgscan and psscan other than that n…
-
```
I think I have a fix for this issue and I am attaching the patch. I don't know
how else to contribute to this project from which I have learned a lot. Thanks
for the good work guys.
What steps …
-
```
When testing netscan, I noticed that for entries without a create time,
(listening sockets for example) that the printed create date was 1/1/70
00:00:00. While most programmers know about this d…
-
```
We need to consider how best to store which plugins work with which profiles.
I think it's probably a facet of the plugin to define which profiles it will
work with, rather than of the profile t…
-
```
There are some plugins (sockets/sockscan) that still show up in the --help
plugins list when a Windows 7 profile is specified. That's because we don't
define Plugin.is_valid_profile for them yet…
-
```
What steps will reproduce the problem?
1. Using the latest volatility with Gentoo 3.12 64bit
2. Used LIME to dump memory image (insmod lime.ko "path=/root/limetest.mem
format=lime"
3. Created Pro…