Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add groups to Payloads #54

Open
AI-Mozi opened this issue Nov 1, 2023 · 6 comments
Open

Add groups to Payloads #54

AI-Mozi opened this issue Nov 1, 2023 · 6 comments
Labels
discussion Topic is open to discussion feature New Feature idea Random idea

Comments

@AI-Mozi
Copy link
Member

AI-Mozi commented Nov 1, 2023

Maybe we could group Payloads at /payloads by their "first part"
(cmd for cmd/awk/reverse_shell, shellcode for shellcode/freebsd/x86/bind_shell etc.)
and then display groups in more horizontal way (as at /db)?

@postmodern
Copy link
Member

So like /payloads/cmd or /payloads/shellcode/freebsd would show all of the payloads under those directories? How would the payload "categories" or "groups" be rendered? Maybe a directory/file tree-like structure? Or maybe only list the top-level directories and force the user to click through them to drill down to /payloads/shellcode/freebsd/x86/?

@postmodern postmodern added discussion Topic is open to discussion idea Random idea feature New Feature labels Nov 1, 2023
@AI-Mozi
Copy link
Member Author

AI-Mozi commented Nov 2, 2023

I thought about something like this:
Screenshot 2023-11-02 at 08 31 09
Leaving routes as they are now and only group hrefs to payloads.

@postmodern
Copy link
Member

@AI-Mozi note that any ronin repo can define their own payloads/ sub-directories. There could be an arbitrary number of payload groups and sub-groups.

@AI-Mozi
Copy link
Member Author

AI-Mozi commented Nov 3, 2023

Oh, so maybe we could display payloads in 3 columns on larger screens, 2 columns on medium screens and 1 column on small screens?

@postmodern
Copy link
Member

@AI-Mozi the number of top-level groups would probably continue to grow over time. I think payloads could be rendered as a list of lists, or a directory tree, or possibly add a search box that filtered the payloads by keyword.

@postmodern
Copy link
Member

Thinking a little more about this. While anyone can add their own payloads via ronin-repos, there will likely be a maximum number of top-level Payload Groups. Metasploit groups their payloads a bit differently, but here's their teir 1 and 2 payload group names:

modules/payloads/adapters:
cmd

modules/payloads/singles:
aix      apple_ios  bsdi  firefox  java   mainframe  osx  python  ruby     tty
android  bsd        cmd   generic  linux  nodejs     php  r       solaris  windows

modules/payloads/stagers:
android  bsd  bsdi  java  linux  multi  netware  osx  php  python  windows

modules/payloads/stages:
android  bsd  bsdi  java  linux  multi  netware  osx  php  python  windows


I would also expect certain Payload Groups to have many more payloads than other Payload Groups. So if we do group payloads by top-level directory as a series divs, we'll need to think about what if one Payload Group is super long and the next one is super short.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Topic is open to discussion feature New Feature idea Random idea
Projects
None yet
Development

No branches or pull requests

2 participants