linkor establish some peer-to-peer connectivity to a running agent.
ParameterType.ConnectionInfo. Now, when you type your command without parameters, you'll get a popup like normal. However, for this type, there will be three dropdown menus for you to fill out:
Payloaddropdown will populate with the associated payloads that Mythic knows are on that host. These payloads are in two main groups:
+next to host, manually specify which host your payload lives on, then select from the dropdown the associated payload that was used. Then click add. Now Mythic is also tracking that the selected payload lives on the indicated host. You can continue with the host/payload/c2_profile dropdowns like normal.
link-command-name hostname other-identifier. The caveat is this now requires the operator to know more detailed information about the connection ahead of time.
ParameterType.ConnectionInfoparameter type is useful when you want to make a new connection between a callback to a payload you just executed or to another callback that your current callback hasn't connected to before. A common command that leverages this parameter type would be
link. However, this isn't too helpful if you want to remove a certain connection or if you just want to re-establish a connection that died. To help with this, there's the
ParameterType.LinkInfowhich, as the name implies, gives information about the links associated with your callback.
ParameterType.LinkInfo, you'll get a dropdown menu where the user can select from live or dead links to leverage. When you select a current/dead link, the data that's sent down to your
create_taskingfunction is the exact same as when you use the
ParameterType.ConnectionInfo- i.e. information about the host, payload uuid, callback uuid, and the p2p c2 profile parameter information.