Changing deployment commands to use implant_name variable instead of static names

mrengstrom commented 3 years ago

Description

changing deployment commands to use the agent.implant_name configuration item instead of sandcat.go

Type of change

Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Started up server with the required change and made sure the deployment commands in the UI had the agent name properly populated with the implant_name, and that it was user configurable from the deployment command page

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[NA] I have made corresponding changes to the documentation
[NA] I have added tests that prove my fix is effective or that my feature works

unkempthenry commented 3 years ago

depends on https://github.com/mitre/caldera/pull/2040

mrengstrom commented 3 years ago

@unkempthenry the GUI options to switch out names are dynamic based on variables in the deploy command. So if you put in a variable it will create a list of the variables to swap out and then check for their presence in app_config dict. So there was no GUI need to add any additional code at the time, unless we wanted to be able to specify a 'default' agent name like we had talked about in the abilities for a given agent (as it would have to be done based on the selected agent, and override the app_config section).

mitre / sandcat