Joe
I've fixed the build constraints, but it appears that there's an upstream Garble issue that prevents the build from succeeding: ``` # github.com/bishopfox/sliver aTZ5WkAu.(*M9GTSgMZEBA9AZ).pnEVb4Qd8: relocation target runtime/internal/atomic.LoadAcquintptr not defined aTZ5WkAu.(*M9GTSgMZEBA9AZ).hw53wf5zL0:...
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.
You'd have to add support to Golang, the Sliver `--os` and `--arch` flags are essentially passed through to the golang compiler.
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?
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...
@n1ete I've merged v0.9.1 of Garble into the Sliver `master` branch if you compile from source you should get the updates.
We'll try to incorporate a refactor in v1.6.x but for now porfwd is not 100% reliable.
If you say 'yes' it should be able to compile a payload for you, some features will just be missing.
I think we're also on an old version of binject and there's been some recent bug fixes too, just haven't had time to take a look yet.