I am not sure how I should make such a request and forgive me if this is the incorrect way to ask.

How can I get a copy of the Petya document that was in the word document spread via MeDoc?

I have seen some links but they're dead and I cannot access them.

Does anyone have a copy ?

Right now the process isn't documented and is done by calling different classes in the project. Make a gradle task and document it a bit to make it easier for people to update it themselves.

Related discussion: CalebFenton/simplify#57

See #88

Some old programs versions can be found here if someone needs them to test old exploits for instance.

There may be some overlap with other signatures, need to verify these samples are 100% independent;

3f98e8d89e42ecafadb529e96c8305707c4a42d9ca97500b91b8da2fc93e07c3
b7a0d51599ff8955f0f77bd946c92433d5241e14fa84e6cbe49e0ad98898ad94
d64e1e2d0847becd4a4cd9c5804e42093719c77c15b2560c2c8bc993e90dda3b
963ee42c96a25f4a5413d8c4c455575e473516aa58c55b575e86a4fbae4aa3aa
bd6d7d8e519a3ba240d8a18d1b22

Wouldn't it be a good idea to create a simple introduction to the system, i.e. how to go from cloning the repo, to actually be able to analyze a file. This would be a great part, such that more people can use the framework.

Describe the bug
Workers need to await a coroutine in order to run in parallel.

To Reproduce
I created a demo to illustrate what I am talking about: https://github.com/ytreister/stoq/tree/workers_in_parallel/demo

You can run scan.py which show the following:
All workers await a coroutine: (This is what I want it to do)

2020-04-19 19:53:19 DEBUG stoq:core.py:scan_request

Hi,

"Example #14: watching a buffer" from http://winappdbg.readthedocs.io/en/latest/Debugging.html doesn't work as expected. Entry/Leave callbacks are correctly called when "ReadFile" is called, however, the read buffer is not watched (the access callback is never called).

I modified the script to print the return value of watch_buffer. It always returns None:

C:\winappdbg> python 14_

The API documentation is not up to date, and the rest of the doc could use some freshening and additions.

We do need some material to compare how far we are currently with the ProcDOT integration. This could be basically achieved by dropping a few samples into a VM monitored by procmon, generating graphs and finally comparing these graphs against ones that are generated by our integration.