While I appreciated the ease of use the tool provides, it offers little flexibility in terms of customizing the chain or porting to other languages. While this is a fantastic tool for most uses, edge cases do exist and need to be addressed.
When it automatically generates chains, it does it in two ways. Firstly, for ones using pushad, it will find several variants (maybe as many as a dozen different chains), and those are all given to the user. For some using a the mov deref / sniper style, it will typically just form the first variant possible. The goal here is to provide a chain that can do the specified task. With respect to customization, we will add more options later to vary some of the inputs, via UI and/or config. An example of that is a pointer to a string needeThanks for checking out the tool. :-) When it automatically generates chains, it does it in two ways. Firstly, for ones using pushad, it will find several variants (maybe as many as a dozen different chains), and those are all given to the user. For some ROP chains using a the mov deref / sniper style, rather than using pushad, it will typically just form the first variant possible. The goal here is to provide a chain that can do the specified task. With respect to customization, we will add more options later to vary some of the inputs, via UI and/or config. An example of of such customization is a pointer to a string needed as a parameter. That may influence the resulting chain to differ in some gadgets being used. The intention is not to offer the users different ways to customize the chain themselves (they can do that manually on their own if they wish), but just to again find at least one that works - or if it is using pushad, then it will provide them with several chains. We are continuously working on this and have several new chains being worked on, to be added to the tool at a later time. We are also working on ways to expand the attack surface, by considering more edge cases and alternative ways of doing things, so stay tuned, as this tool is under active development and continuously evolving. There are also other new, unrelated features under active development. d as a parameter. That may influence the resulting chain to differ in some gadgets being used. The intention is not to offer the users different ways to customize the chain themselves (they can do that manually on their own if they wish), but just to again find at least one that works - or if it is using pushad, then it will provide them with several chains. We are continuously working on this and have several new chains being worked on, to be added to the tool at a later time. We are also working on ways to expand the attack surface, by considering more edge cases and alternative ways of doing things, so stay tuned, as this tool is under active development and continuously evolving. There are also other new, unrelated features under active development.
While I appreciated the ease of use the tool provides, it offers little flexibility in terms of customizing the chain or porting to other languages. While this is a fantastic tool for most uses, edge cases do exist and need to be addressed.
When it automatically generates chains, it does it in two ways. Firstly, for ones using pushad, it will find several variants (maybe as many as a dozen different chains), and those are all given to the user. For some using a the mov deref / sniper style, it will typically just form the first variant possible. The goal here is to provide a chain that can do the specified task. With respect to customization, we will add more options later to vary some of the inputs, via UI and/or config. An example of that is a pointer to a string needeThanks for checking out the tool. :-) When it automatically generates chains, it does it in two ways. Firstly, for ones using pushad, it will find several variants (maybe as many as a dozen different chains), and those are all given to the user. For some ROP chains using a the mov deref / sniper style, rather than using pushad, it will typically just form the first variant possible. The goal here is to provide a chain that can do the specified task. With respect to customization, we will add more options later to vary some of the inputs, via UI and/or config. An example of of such customization is a pointer to a string needed as a parameter. That may influence the resulting chain to differ in some gadgets being used. The intention is not to offer the users different ways to customize the chain themselves (they can do that manually on their own if they wish), but just to again find at least one that works - or if it is using pushad, then it will provide them with several chains.
We are continuously working on this and have several new chains being worked on, to be added to the tool at a later time.
We are also working on ways to expand the attack surface, by considering more edge cases and alternative ways of doing things, so stay tuned, as this tool is under active development and continuously evolving. There are also other new, unrelated features under active development. d as a parameter. That may influence the resulting chain to differ in some gadgets being used. The intention is not to offer the users different ways to customize the chain themselves (they can do that manually on their own if they wish), but just to again find at least one that works - or if it is using pushad, then it will provide them with several chains.
We are continuously working on this and have several new chains being worked on, to be added to the tool at a later time.
We are also working on ways to expand the attack surface, by considering more edge cases and alternative ways of doing things, so stay tuned, as this tool is under active development and continuously evolving. There are also other new, unrelated features under active development.