Joe
I was just taking a look at this as well, I think we can probably fit it into v1.5
yes, but it's not user-friendly, you can used advanced options to force a resolv.conf - https://github.com/BishopFox/sliver/wiki/C2-Advanced-Options#dns-c2-advanced-options Note even on windows it needs to be formatted as a `resolv.conf` file including...
Compiling the implant with `--debug` may give you more information about what's going on, I'm guessing it's simply a matter of getting the syntax of the command correct. One notable...
Interesting, not sure what's going wrong based on your description / log output. Are there any errors in the server logs? (`~/.sliver/logs/sliver.log`)
Depending on how adventurous you are we did play around with adding [go-lua](https://github.com/BishopFox/sliver/tree/go-lua) but it's not ready for prime time yet.
Duplicate of issue #28
Are you using a terminal that supports PTYs?
Interesting, I'll see if i can reproduce, give `shell --no-pty` a try as I suspect its related to PTYs in some way.
Okay, we'll try to reproduce likely some issue specific to the Windows Terminal implementation of pty/stdin/out
The limit should be ~2Gb, will investigate.