-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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 fetch payloads for aarch64, armbe, armle, mipsbe, mipsle, ppc, ppc64 #19850
base: master
Are you sure you want to change the base?
Conversation
AARCH64 STAGELESS
EDIT (@dledda-r7) AARCH64 STAGEDUsing qemu-aarch64-static
|
ARMEL
This system did not have cURL or TFTP |
MIPSLE
|
Hey @dledda-r7 as per our slack discussion I'm just linking this testing done by @h00die-gr3y who found an issue when testing the staged versions of some of the newly supported architectures for fetch payloads. |
MIPSBE
|
Closes #19848 |
Co-authored-by: Christophe De La Fuente <[email protected]>
Co-authored-by: Christophe De La Fuente <[email protected]>
Co-authored-by: Christophe De La Fuente <[email protected]>
Co-authored-by: Christophe De La Fuente <[email protected]>
Co-authored-by: Christophe De La Fuente <[email protected]>
Ok so, so far I am able to get a fetch payload for:
I am having issue with the PPC64... so far looks like we have meterpreter only for PPC64LE, but for PPC64(BE) we have couple of payloads that should(?) be supported:
@bwatters-r7 let me know what is the best move for this, other than this little thing everything looks good to me. |
@dledda-r7 I did not make those because I did not think we had any demand or targets for them. I can add them if we want, but since we have at least 1 PR blocked waiting for this PR, it might be better to mark it as an issue and add them later. |
Adding several arch adapters to increase fetch payload coverage.
Please await testing.