-
```
What steps will reproduce the problem?
1. use an uncompress hpak memory dump
2. create a string file from mem using strings -q -o mem.img>raw_strings.txt
3. run volatility using -f mem.img string…
-
```
What steps will reproduce the problem?
1. use an uncompress hpak memory dump
2. create a string file from mem using strings -q -o mem.img>raw_strings.txt
3. run volatility using -f mem.img string…
-
```
What steps will reproduce the problem?
1. use an uncompress hpak memory dump
2. create a string file from mem using strings -q -o mem.img>raw_strings.txt
3. run volatility using -f mem.img string…
-
```
What steps will reproduce the problem?
1. use an uncompress hpak memory dump
2. create a string file from mem using strings -q -o mem.img>raw_strings.txt
3. run volatility using -f mem.img string…
-
```
What steps will reproduce the problem?
1. use an uncompress hpak memory dump
2. create a string file from mem using strings -q -o mem.img>raw_strings.txt
3. run volatility using -f mem.img string…
-
```
What steps will reproduce the problem?
1. use an uncompress hpak memory dump
2. create a string file from mem using strings -q -o mem.img>raw_strings.txt
3. run volatility using -f mem.img string…
-
```
What steps will reproduce the problem?
1. use an uncompress hpak memory dump
2. create a string file from mem using strings -q -o mem.img>raw_strings.txt
3. run volatility using -f mem.img string…
-
`compile` command should take an optional [`deviceID`, `platformID` and `productID`](https://github.com/spark/sparkjs/blob/master/lib/spark-api.js#L382) parameters and pass them to the API.
-
```
What steps will reproduce the problem?
1. use an uncompress hpak memory dump
2. create a string file from mem using strings -q -o mem.img>raw_strings.txt
3. run volatility using -f mem.img string…
-
```
What steps will reproduce the problem?
1. use an uncompress hpak memory dump
2. create a string file from mem using strings -q -o mem.img>raw_strings.txt
3. run volatility using -f mem.img string…