Viyat

@EXTREMOPHILARUM can you actually go over the entire codebase and change it to `safe_load`? This is vulnerability where a malicious YAML can trigger an RCE on OWTF :)

Yes, +1 This could make the code substantially easier to read, modify and also useful when writing custom plugins.

_From @DePierre on August 8, 2015 17:9_ Not sure about the classification but I agree about the "each type of one plugin into one file" idea, browsing the plugins is...

_From @tunnelshade on August 8, 2015 18:56_ @DePierre The present classification is for the end user and it is perfect. What I am suggesting in Classification is the class hierarchy....

_From @DePierre on August 8, 2015 19:32_ @tunnelshade OK for the classification for the end users. The more I think about it, the more it is likely that the classes...

_From @tunnelshade on August 8, 2015 19:34_ +1 on the context manager. One base class should do only because we use multiple things in multiple places. Yes, we can never...

_From @DePierre on August 8, 2015 19:40_ I don't like how "we use multiple things in multiple places" sounds :D Sounds like a mess. I am scared that we will...

_From @tunnelshade on August 8, 2015 19:44_ I too don't like the sound. But the problem is we run commands in all Passive, SemiPassive and Active. External only shows resources....

_From @DePierre on August 8, 2015 19:46_ @tunnelshade I guess that is downside of have a gap between the dev classification and the end-user one. But I strongly believe that...

_From @tunnelshade on August 8, 2015 19:55_ Not much classification but How is this? - Grep plugins will have a seperate base plugin - External plugins will have a seperate...