Hi, hope you are well. Here I am with a modest contribution.
Donut allows to pass arguments to the generated shellcode, so I added the functionnality to pass arguments.
Here is an example use case :
I want to always build Seatbelt using the -group=all argument > I can change the toolArguments value in the yaml description of Seatbelt, and the arguments will automatically be embedded in the shellcode at every build.
One day, I decide I want to have a special Seatbelt shellcode, and override the "-group=all" argument with another one, I can simply do OffensivePipeline.exe t seatbelt -a "-mynew=argument". This special build will override the yaml conf only this time.
If I never supply -a, and never set toolArguments in yaml, then everything works like it worked before (i.e. no argument embedded)
If I build using all, then -a is obviously not available anymore, and the toolsArguments of the yaml configs will be used.
Hi, hope you are well. Here I am with a modest contribution. Donut allows to pass arguments to the generated shellcode, so I added the functionnality to pass arguments. Here is an example use case :
-group=allargument > I can change the toolArguments value in the yaml description of Seatbelt, and the arguments will automatically be embedded in the shellcode at every build.OffensivePipeline.exe t seatbelt -a "-mynew=argument". This special build will override the yaml conf only this time.-a, and never set toolArguments in yaml, then everything works like it worked before (i.e. no argument embedded)-ais obviously not available anymore, and the toolsArguments of the yaml configs will be used.