-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Generate mips implants failling with rpc error: code = Unknown desc = exit status 2 #1064
Comments
We technically don't support MIPS, but it should build the stock executable. Looks like a bug in the Linux build constraints that causes a CGO dependency to be included in the build. |
IIRC those imports are for the screenshot feature. |
I'm guessing our build constraint is only for Linux and not Linux/amd64 |
Yes that would make sense. |
Looking at that lib, it seems to supports i386, amd64 and arm64 so we should probably restrict to that. Also, a quick search seems to imply that all the SHM syscall numbers (used by the |
I've fixed the build constraints, but it appears that there's an upstream Garble issue that prevents the build from succeeding:
For now you have to build with |
This is potentially fixed in upstream Garble as we're a little behind their latest release, we should update our internal Garble before filing an upstream issue. |
Is it possible to point to custom garble for building? |
Seems like i didnt pay attention to the build architecture of my target hosts that i want to control. |
You'd have to add support to Golang, the Sliver |
ok building mips beacons/implants went fine with the fix in #1066. and it should run afaik with gooarch=mips but i tried all mips builds (just in case i missed some releveant information)
however running the binary on the devices returns:
any ideas ? |
If there is an issue with the compiled binary (that's not a stack trace) it's likely an issue with upstream Go. |
@n1ete it looks like the machine may be trying to execute it as a shell script instead of a native binary? |
@moloch-- OS is openwrt |
I'd look to see if anyone in the wider Go community has run into this problem or managed to solve it, if you can get any Go program to run on the target device you should be able to get the generic version of the Sliver implant running (the generic version is pure Go). |
Thanks, if you need further debug data i am happy to provide them to you. I have a few different boxes laying around with these chip-sets. i stumbled upon |
We're going to fix it soon: burrowers/garble#646 |
The issue above is fixed with yesterday's garble v0.9.1 release. |
@n1ete I've merged v0.9.1 of Garble into the Sliver |
Still some problems with building for mips.
this is the command i used
here the corresponding server logs
also i see frequently these messages in the logs .....thinking this is LXC container related...
The text was updated successfully, but these errors were encountered: