Joe
We've actually been thinking about how to implement this in a good way for a long time, and I think I have an approach in my head that I'm going...
Yea, i think the way I'm going to implement this is a general way to export the implant configuration to an external builder, the build can build anything then upload...
Yeap, that's basically how I did it (see PR above) --though it uses the existing gRPC/mTLS API instead of REST. However, we can just implement REST in middleware if someone...
The low level APIs are now in `master` but I'll create an basic builder too. We can turn any server binary into an external builder by creating a new cli...
https://github.com/BishopFox/sliver/pull/943
https://github.com/BishopFox/sliver/wiki/External-Builders
The go http client makes a best effort to identify the proxy settings, you probably want to use the `wininet` driver to strictly adhere to the Windows system proxy settings,...
So for the Go http library we use a modified [go get proxied library](https://github.com/rapid7/go-get-proxied) located here in the code base: https://github.com/BishopFox/sliver/tree/master/implant/sliver/proxy Which currently does employ multiple methods of identifying the...
Yeap! There's for sure improvements we can still make to this, so feel free to send us PRs still. You can also force proxy settings via the c2 advanced options...
Yea we need to find a way to have better UX around this feature.