If running more than one module at the same time, output gets mixed up

[byt3bl33d3r]

Sessions run modules/tasks asynchronously, the way this is currently implemented (threads) has the unfortunate consequence of mixing up module's output if more than one is running at the same time because we're just hooking STDout using Console.SetOutput(). (https://github.com/byt3bl33d3r/SILENTTRINITY/blob/master/core/teamserver/data/stage.boo#L359-L379)

We really have only two options (unless i'm missing something obvious) to fix this:

1. We run each module in it's own separate process instead of a thread (which would allow us to keep using the print statement for a modules output but would complicate the code considerably )
2. Pass a new StringBuilder() object to each module and append the output to it (this would allow us to keep using threads but we won't be able to use the print statement anymore to handle output which is really pretty)

[byt3bl33d3r]

Turns out this is a lot more complicated problem than I thought. The only way around this seems to be solution n2 and forgo redirecting Stdout all together.

[baconwaifu]

Would it be possible to modify the parser so each instance can have it's own TextWriter as "stdout"? The main scheduler can then buffer and order it appropriately without significantly increasing complexity, or breaking existing modules. Console is just a static wrapper around a TextWriter anyways.

[jayrod]

Option n2 might allow for alternate data from one command. Like it'd be great to output the ps module in both human readable format and also parsable.