Shellcode database

[ColdHeat]

Gather all of the shellcode in the shellcode repo into a sqllite database. Each piece of shellcode should accept arguments to control things like IP addresses and ports.

I would probably assemble the shellcode before creating the database and then properly insert variables into the bytes. This can become convoluted. It may be better to store strings of ASM and then assemble the shellcode at runtime.

[kiwiz]

Nasm allows you to define macros by passing in args. Ex: nasm -D cat=0x1234 test.s -o test

[evanpjensen]

There is currently no way to build all the shellcode at once. The build system is pretty messy (read: beautiful.) If you want to research build systems and write a script that builds everything at once and populates a database that would be great. I still think the idea of binary patching shellcode before exploitation with settings and such makes for brittle systems because the shellcode is subject to change at any time.

On Mon, Feb 17, 2014 at 9:36 AM, Kai notifications@github.com wrote:

Nasm allows you to define macros by passing in args. Ex: nasm -D cat=0x1234 test.s -o test

Reply to this email directly or view it on GitHubhttps://github.com/isislab/autosockets/issues/5#issuecomment-35286637 .