From b27bd998532a334794ec397853c9e98469b71c5d Mon Sep 17 00:00:00 2001 From: spenceradolph Date: Sun, 14 Apr 2024 19:12:18 +0000 Subject: [PATCH] updated readme with install --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index fb9a16f..90b06fc 100644 --- a/README.md +++ b/README.md @@ -148,13 +148,13 @@ sudo ./mythic-cli install github https://github.com/MythicAgents/sliver When it's time for you to test out your install or for another user to install your agent, it's pretty simple. Within Mythic is a `mythic-cli` binary you can use to install agents: - `sudo ./mythic-cli install github https://github.com/user/repo` to install the main branch -- `sudo ./mythic-cli install github https://github.com/user/repo branchname` to install a specific branch of that repo +* `sudo ./mythic-cli install github https://github.com/user/repo -b branchname` to install a specific branch of that repo Now, you might be wondering _when_ should you or a user do this to properly add your agent to their Mythic instance. There's no wrong answer here, just depends on your preference. The three options are: -- Mythic is already up and going, then you can run the install script and just direct that agent's containers to start (i.e. `sudo ./mythic-cli payload start agentName` and if that agent has its own special C2 containers, you'll need to start them too via `sudo ./mythic-cli c2 start c2profileName`). -- Mythic is already up and going, but you want to minimize your steps, you can just install the agent and run `sudo ./mythic-cli mythic start`. That script will first _stop_ all of your containers, then start everything back up again. This will also bring in the new agent you just installed. -- Mythic isn't running, you can install the script and just run `sudo ./mythic-cli mythic start`. +* Mythic is already up and going, then you can run the install script and just direct that agent's containers to start (i.e. `sudo ./mythic-cli start agentName` and if that agent has its own special C2 containers, you'll need to start them too via `sudo ./mythic-cli start c2profileName`). +* Mythic is already up and going, but you want to minimize your steps, you can just install the agent and run `sudo ./mythic-cli start`. That script will first _stop_ all of your containers, then start everything back up again. This will also bring in the new agent you just installed. +* Mythic isn't running, you can install the script and just run `sudo ./mythic-cli start`. ## Local Development Notes