Cale Black
Cale Black
Having every function prefixed with Random is redundant and can sometimes cause more confusion than it helps. This is a pretty big change and should not be merged until supported...
As per the debugging session in chat the `-proxy` handling does not work as expected under some conditions. This for example works in `httphelpers.go` but not the `ProxyFromEnvironment`: ```go Proxy:...
Currently the `DisableC2` doesn't disable the `-lhost` or `-lport` checks so they need to be set when they are and then rechecked when startup happens.
Closes #234 Allows for protocols to have explicit flags that will resolve when they get defined. For example, if your exploit defines "HTTP" as it's protocol, this change automatically applies...
Part of #189 This is the first pass at adding a basic artifact storage to the framework. Changes are: - Add a SQL table for a really basic artifact set...
Adds a set off helper functions to help chain ASP.NET application state management functions. Historically, ASP.NET apps have been a bit of a nuisance to work with because of the...
This adds support for adding explicit payload support to an exploit. This provides a few things: - *Bring Your Own Payload* (BYOP). Long awaited ability to support user provided payloads....
As discussed on our call, add a new payload "type" option that allows for the exploit author to specify what type of payload is supported by the exploit. This will...
This proposal is to replace the very large (and growing) pile of options for `protocol` with a [functional options](https://github.com/teivah/100-go-mistakes/blob/master/src/02-code-project-organization/11-functional-options/functional-options/main.go) pattern. I also propose that we adopt either the functional options...
We have some `.so` ELF reverse shell we build with nasm in our private repos that are good for path injection or preload attacks. Migrate those into `go-exploit`