Joe
The server log may contain errors `~/.sliver/logs/sliver.log` but the default log level is `info` so it may be incomplete depending on the nature of the failure; probably worth checking to...
Not necessary, the tunnel code needs a fresh coat of paint to address issues like this. Please let us know if you find a reliable method to produce the behavior...
Make sure you're using Go 1.22 with `master` the sliver server and client should compile without issue, you can use also `make linux-arm64`. However, cross-compiling a Windows implant to shellcode...
Current master should build to ARM now due to a switch to Zig for CGO really simplifies cross architecture stuff.
@rkervella is this something weird to do with the `stdout` shenanigans?
Likely an issue with your local metasploit installation, for stagers we just call the msfvenom APIs
Make sure its on the `PATH` of the Sliver server's user (probably root).
We've been considering configurable go versions in v1.6.x already as v1.20 will be the last to support Windows 7, so being able to go back to older versions seems useful...
Looks like you're missing [`--prepend-size`](https://github.com/BishopFox/sliver/wiki/Stagers#metasploit-bring-your-own-stager)
can you enable debug mode and send us the full stack trace