Cale Black

After some thinking on this we should probably do a few things: 1. Avoid adding global flags that are protocol assumptive. 2. Match on the `config.Protocol` and for a known...

Artifact is the right term imo based on [NIST Glossary](https://csrc.nist.gov/glossary/term/artifact) but I know was contentious, maybe "evidence"?

This is definitely one I don't want to casually merge for the same reason. I've done one push to a private repo for how to make this work. There's also...

# The clear parts - Simple interfaces & channel type The core part of this is to expose a "channel" type to replace the host port juggling and allow for...

I also am going to make a larger change to support multiple of the same Impl types before we merge this. PR link coming soon

I'm pretty happy with where this is at now and have some demos in the works. I believe I am prepared for a review.

@mahadzaryab1 absolutely! We always welcome any contribution and this would be a great one to start getting familiar with `go-exploit`. :)

Fair and reasonable. I considered deprecating the old functions but leaving them to keep stability. I'll make a issue and maybe add a "api-break" change comment leading here.

Utilities is also a very overloaded term. Instead I might focus on specific servers and just call them that explicitly.

Updated with our offline discussion of moving it to `protocol` vs `cli` which I think is smart: Negative case: ```console poptart@grimm $ make && ./build/cve-2024-4548* -h 2>&1 | grep -A...