Joe
I'll have to take a look, i'm not sure we can safely pass the connections to multiple goroutines without needing a variety of locks to prevent race conditions.
From a glance I think we're better off implementing a multiplexer using something like [smux](https://github.com/xtaci/smux)
The RAM and CPU requirements can be drastically reduced by disabling symbol obfuscation (and/or using an [external builder](https://github.com/BishopFox/sliver/wiki/External-Builders)). The code obfuscator (and to a lesser extent the Go compiler itself)...
Can you pull the errors from `~/.sliver/logs/sliver.log` cross-compiling to Linux from MacOS is always a bit of a pain because you need a C compiler and to link against musl....
There's a bug in the most recent version, use v1.5.39
Can you pull the server logs from `~/.sliver/logs/sliver.log`?
Your HTTP C2 config file invalid, you can manually edit it or delete it to revert to the defaults, the HTTP C2 file is located at `~/.sliver/configs/http-c2.json`
TBC: The RPC error message is a generic "build failed" message, builds can fail for a variety of reasons, you have to look at the server log for the detailed...
@n1ete it looks like you're also cross-compiling a shared library to MIPS, shared library builds require cross-compilers to work so you'll need to install a CGO MIPS cross-compiler. Normal standalone...
@n1ete a third issue is also that Golang simply doesn't support shared library builds for linux/mips https://github.com/golang/go/issues/43264