You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I am customizing the sliver implant for an engagement, per this url, I should modify the source code under implant and register the resulting sliver-server binary as an external builder. The targets of this engagement is running ARMv7 Linux (which is not a supported compiler target, I know).
To Reproduce
Steps to reproduce the behavior:
Register the default sliver-server binary as an external builder
Generate an implant using an unsupported combo of OS / Arch:
sliver > generate beacon --arch arm --os linux --http http://test.c2.com -s /tmp/custom-implant --external-builder
⚠️ Unsupported compiler target linux/arm, but we can try to compile a generic implant.
⚠️ Generic implants do not support all commands/features.
? Attempt to build generic implant? Yes
sliver>....
On the external builder side, I don't see it outputting anything
Expected behavior
The external builder should be able to build generic implants. If not, it should tell the operator.
Screenshots
Desktop (please complete the following information):
OS: Linux AMD64
Version 1.5.42
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
I am customizing the sliver implant for an engagement, per this url, I should modify the source code under
implant
and register the resultingsliver-server
binary as an external builder. The targets of this engagement is running ARMv7 Linux (which is not a supported compiler target, I know).To Reproduce
Steps to reproduce the behavior:
On the external builder side, I don't see it outputting anything
Expected behavior
The external builder should be able to build generic implants. If not, it should tell the operator.
Screenshots
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: