Skip to content

Organization plan #4

@evanpjensen

Description

@evanpjensen

come up with a plan to logically organize all of the shellcode. I like the system I have now of using make files to generate executables for testing but it is a little tedious. The names for almost all of the shellcode folders is unclear. Come up with a system for testing difficult shellcode like staggers and socket reuse code.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions