Mythic
Mythic copied to clipboard
its-a-feature
Auto-scroll in `console view` and rendering responses
Hi there,
in “console view” there is no auto-scroll to see the output, so after pressing enter to send a command you have to move the hand and scroll to see the output every time.
One more “bug” I noticed - when you are doing ls, at first you get the raw output (without browser script - first screenshot), so if you want to get the “rendered” view (2nd screenshot) you need to click on another task and then click back on the ls task to see the formatted view. when you navigate in the filesystem of a victim and look for interesting files, it isn't very pleasant to do so every time (every ls)
raw output:
after click on another task and coming back to the task, the result is fine:
in both cases, this was checked on macOS Sonoma 14.5 (m2), with poseidon agent.
Once this latest build is done (https://github.com/its-a-feature/Mythic/actions/runs/10148225060) can you give that a shot? I added a bunch of UI updates to help with this and the auto scrolling issues. It's for Mythic 3.3 though.
Yes i will! How to upgrade existing Mythic to branch 3.3 (if its not in master) ? I don't to mess things up so asking nooby question. Thanks!
No worries! I wouldn't recommend upgrades during an assessment, so if you're actively operating for something then I'd suggest holding off. Since Mythic3.3 is currently in beta as we're testing out some new features, the process is a little more involved, but not much. Essentially:
- checkout Mythic 3.3
- sudo make (as usual) to get the new mythic-cli binary
- install the Mythic3.3 version of agents/c2 (ex:
sudo ./mythic-cli install github https://github.com/MythicAgents/poseidon -b Mythic3.3 -f) - repeat for each c2 and agent you're using (note: not all might have a Mythic3.3 beta branch currently, https://mythicmeta.github.io/overview/)
- sudo ./mythic-cli start
@its-a-feature I'm unsure what is wrong, but i can't get the Mythic3.3 or maybe you forgot to update the sidebar UI? I did the steps twice but still version is v3.2.20-rc7. how can i be sure i'm on Mythic3.3?
also, this error popped up (and i cannot work with posiedon anymore):
Log from upgrading to Mythic3.3
ubuntu@ip-10-0-9-160:~/Mythic$ git pull
remote: Enumerating objects: 665, done.
remote: Counting objects: 100% (665/665), done.
remote: Compressing objects: 100% (185/185), done.
remote: Total 665 (delta 447), reused 652 (delta 434), pack-reused 0
Receiving objects: 100% (665/665), 13.38 MiB | 15.54 MiB/s, done.
Resolving deltas: 100% (447/447), completed with 14 local objects.
From https://github.com/its-a-feature/Mythic
2203c84e..1f368b4b Mythic3.3 -> origin/Mythic3.3
* [new tag] v0.0.4.17 -> v0.0.4.17
* [new tag] v0.0.4.10 -> v0.0.4.10
* [new tag] v0.0.4.11 -> v0.0.4.11
* [new tag] v0.0.4.12 -> v0.0.4.12
* [new tag] v0.0.4.13 -> v0.0.4.13
* [new tag] v0.0.4.14 -> v0.0.4.14
* [new tag] v0.0.4.15 -> v0.0.4.15
* [new tag] v0.0.4.16 -> v0.0.4.16
* [new tag] v0.0.4.3 -> v0.0.4.3
* [new tag] v0.0.4.4 -> v0.0.4.4
* [new tag] v0.0.4.5 -> v0.0.4.5
* [new tag] v0.0.4.6 -> v0.0.4.6
* [new tag] v0.0.4.7 -> v0.0.4.7
* [new tag] v0.0.4.8 -> v0.0.4.8
* [new tag] v0.0.4.9 -> v0.0.4.9
Already up to date.
ubuntu@ip-10-0-9-160:~/Mythic$ git checkout -b Mythic3.3
Switched to a new branch 'Mythic3.3'
ubuntu@ip-10-0-9-160:~/Mythic$ sudo make
cd Mythic_CLI && make build_linux && mv mythic-cli ../
make[1]: Entering directory '/home/ubuntu/Mythic/Mythic_CLI'
docker run -v /home/ubuntu/Mythic/Mythic_CLI/copy_file/:/copy_file/ --rm ghcr.io/its-a-feature/mythic_cli:v0.0.3.53 sh -c "cp /mythic-cli_linux /copy_file/mythic-cli"
mv ./copy_file/mythic-cli . && rm -rf ./copy_file && chmod +x mythic-cli
make[1]: Leaving directory '/home/ubuntu/Mythic/Mythic_CLI'
ubuntu@ip-10-0-9-160:~/Mythic$ sudo ./mythic-cli install github https://github.com/MythicAgents/poseidon -b Mythic3.3 -f
2024/08/06 07:12:39 [*] Creating temporary directory
2024/08/06 07:12:39 [*] Cloning branch "Mythic3.3" from https://github.com/MythicAgents/poseidon
Cloning into '/home/ubuntu/Mythic/tmp'...
2024/08/06 07:12:41 [*] Parsing config.json
[*] Processing Payload Type poseidon
2024/08/06 07:12:41 [*] Stopping current container
WARN[0000] /home/ubuntu/Mythic/docker-compose.yml: `version` is obsolete
[+] Stopping 1/1
✔ Container poseidon Stopped10.2s
2024/08/06 07:12:51 [*] Removing current version
2024/08/06 07:12:51 [+] Successfully removed the current version
2024/08/06 07:12:51 [*] Copying new version of payload into place
2024/08/06 07:12:51 [*] Adding service into docker-compose
2024/08/06 07:12:51 [*] Removing old volume, poseidon_volume, if it exists
WARN[0000] /home/ubuntu/Mythic/docker-compose.yml: `version` is obsolete
[+] Stopping 1/0
✔ Container poseidon Stopped0.0s
Going to remove poseidon
[+] Removing 1/1
✔ Container poseidon Removed0.5s
WARN[0000] /home/ubuntu/Mythic/docker-compose.yml: `version` is obsolete
[+] Running 20/1
✔ poseidon Pulled 148.2s 1.67GB / 1.67GB Pulling 148.1s
[+] Running 1/1
✔ Container poseidon Started2.6s
2024/08/06 07:15:24 [+] Successfully installed service
2024/08/06 07:15:24 [+] Successfully installed c2
2024/08/06 07:15:24 [*] Processing Documentation for poseidon
2024/08/06 07:15:24 [*] Removing current version
2024/08/06 07:15:24 [+] Successfully removed the current version
2024/08/06 07:15:24 [*] Copying new documentation into place
2024/08/06 07:15:24 [+] Successfully installed Payload documentation
2024/08/06 07:15:24 [+] Successfully installed c2 documentation
2024/08/06 07:15:24 [+] Successfully installed Wrapper documentation
[*] Restarting mythic_documentation container to pull in changes
WARN[0000] /home/ubuntu/Mythic/docker-compose.yml: `version` is obsolete
[+] Stopping 1/1
✔ Container mythic_documentation Stopped0.3s
WARN[0000] /home/ubuntu/Mythic/docker-compose.yml: `version` is obsolete
[+] Stopping 1/0
✔ Container mythic_documentation Stopped0.0s
WARN[0000] /home/ubuntu/Mythic/docker-compose.yml: `version` is obsolete
[+] Running 1/1
✔ Container mythic_documentation Started0.5s
2024/08/06 07:15:26 [*] Waiting for RabbitMQ to come online (Retry Count = 10)
2024/08/06 07:15:26 [*] Attempting to connect to RabbitMQ at 127.0.0.1:5672, attempt 1/10
2024/08/06 07:15:26 [+] Successfully connected to RabbitMQ at amqp://mythic_user:***@127.0.0.1:5672/mythic_vhost
2024/08/06 07:15:26 [*] Waiting for Mythic Server and Nginx to come online (Retry Count = 10)
2024/08/06 07:15:26 [*] Attempting to connect to Mythic UI at https://127.0.0.1:7443, attempt 1/10
2024/08/06 07:15:26 [+] Successfully connected to Mythic at https://127.0.0.1:7443
MYTHIC SERVICE WEB ADDRESS BOUND LOCALLY
Nginx (Mythic Web UI) https://127.0.0.1:7443 false
Mythic Backend Server http://127.0.0.1:17443 true
Hasura GraphQL Console http://127.0.0.1:8080 true
Jupyter Console http://127.0.0.1:8888 true
Internal Documentation http://127.0.0.1:8090 true
ADDITIONAL SERVICES ADDRESS BOUND LOCALLY
Postgres Database postgresql://mythic_user:[email protected]:5432/mythic_db true
React Server http://127.0.0.1:3000/new true
RabbitMQ amqp://mythic_user:[email protected]:5672 true
Mythic Main Services
CONTAINER NAME STATE STATUS MOUNT PORTS
mythic_documentation running Up Less than a second (health: starting) local 8090/tcp -> 127.0.0.1:8090
mythic_graphql running Up 4 weeks (healthy) N/A 8080/tcp -> 127.0.0.1:8080
mythic_jupyter running Up 4 weeks (healthy) local 8888/tcp -> 127.0.0.1:8888
mythic_nginx running Up 4 weeks (healthy) local 7443/tcp -> :::7443, 7443
mythic_postgres running Up 4 weeks (healthy) local 5432/tcp -> 127.0.0.1:5432
mythic_rabbitmq running Up 4 weeks (healthy) local 5672/tcp -> 127.0.0.1:5672
mythic_react running Up 4 weeks (healthy) local 3000/tcp -> 127.0.0.1:3000
mythic_server running Up 4 weeks (healthy) local 7000/tcp -> :::7000, 7001/tcp -> :::7001, 7002/tcp -> :::7002, 7003/tcp -> :::7003, 7004/tcp -> :::7004, 7005/tcp -> :::7005, 7006/tcp -> :::7006, 7007/tcp -> :::7007, 7008/tcp -> :::7008, 7009/tcp -> :::7009, 7010/tcp -> :::7010, 17443/tcp -> 127.0.0.1:17443, 17444/tcp -> 127.0.0.1:17444, 7000, 7001, 7002, 7003, 7004, 7005, 7006, 7007, 7008, 7009, 7010
Installed Services
CONTAINER NAME STATE STATUS MOUNT
apfell running Up 4 weeks apfell_volume
apollo running Up 4 weeks local
athena running Up 4 weeks athena_volume
http running Up 4 weeks http_volume
merlin running Up 4 weeks local
nimsyscallpacker_wrapper running Up 4 weeks local
poseidon running Up 2 seconds poseidon_volume
venus running Up 4 weeks local
websocket running Up 4 weeks websocket_volume
2024/08/06 07:15:26
[*] RabbitMQ is currently listening on localhost. If you have a remote Service, they will be unable to connect (i.e. one running on another server)
2024/08/06 07:15:26
Use 'sudo ./mythic-cli config set rabbitmq_bind_localhost_only false' and restart mythic ('sudo ./mythic-cli restart') to change this
2024/08/06 07:15:26
[*] MythicServer is currently listening on localhost. If you have a remote Service, they will be unable to connect (i.e. one running on another server)
2024/08/06 07:15:26
Use 'sudo ./mythic-cli config set mythic_server_bind_localhost_only false' and restart mythic ('sudo ./mythic-cli restart') to change this
2024/08/06 07:15:26 [*] If you are using a remote PayloadType or C2Profile, they will need certain environment variables to properly connect to Mythic.
2024/08/06 07:15:26 Use 'sudo ./mythic-cli config service' for configs for these services.
[+] Successfully installed service!
ubuntu@ip-10-0-9-160:~/Mythic$ sudo ./mythic-cli restart
WARN[0000] /home/ubuntu/Mythic/docker-compose.yml: `version` is obsolete
[+] Stopping 17/17
✔ Container poseidon Stopped10.1s
✔ Container websocket Stopped10.8s
✔ Container mythic_react Stopped1.7s
✔ Container apollo Stopped10.9s
✔ Container venus Stopped10.9s
✔ Container athena Stopped10.8s
✔ Container mythic_documentation Stopped1.6s
✔ Container http Stopped10.4s
✔ Container mythic_server Stopped2.6s
✔ Container apfell Stopped10.5s
✔ Container merlin Stopped10.9s
✔ Container mythic_graphql Stopped11.0s
✔ Container mythic_postgres Stopped1.8s
✔ Container nimsyscallpacker_wrapper Stopped10.3s
✔ Container mythic_jupyter Stopped2.7s
✔ Container mythic_nginx Stopped1.2s
✔ Container mythic_rabbitmq Stopped7.2s
WARN[0000] /home/ubuntu/Mythic/docker-compose.yml: `version` is obsolete
[+] Running 13/13
✔ Container mythic_graphql Started3.4s
✔ Container mythic_react Started4.0s
✔ Container athena Started1.4s
✔ Container mythic_postgres Started4.8s
✔ Container mythic_rabbitmq Started4.4s
✔ Container mythic_documentation Started4.3s
✔ Container mythic_nginx Started4.2s
✔ Container mythic_jupyter Started4.4s
✔ Container mythic_server Started5.1s
✔ Container poseidon Started1.3s
✔ Container websocket Started1.4s
✔ Container apfell Started1.7s
✔ Container http Started1.6s
WARN[0000] /home/ubuntu/Mythic/docker-compose.yml: `version` is obsolete
[+] Running 4/4
✔ Container merlin Started1.9s
✔ Container apollo Started1.6s
✔ Container nimsyscallpacker_wrapper Started1.7s
✔ Container venus Started1.4s
2024/08/06 07:18:37 [*] Waiting for RabbitMQ to come online (Retry Count = 10)
2024/08/06 07:18:37 [*] Attempting to connect to RabbitMQ at 127.0.0.1:5672, attempt 1/10
2024/08/06 07:18:37 [-] Failed to connect to RabbitMQ, retrying in 10s
2024/08/06 07:18:47 [*] Attempting to connect to RabbitMQ at 127.0.0.1:5672, attempt 2/10
2024/08/06 07:18:47 [-] Failed to connect to RabbitMQ, retrying in 10s
2024/08/06 07:18:57 [*] Attempting to connect to RabbitMQ at 127.0.0.1:5672, attempt 3/10
2024/08/06 07:18:57 [-] Failed to connect to RabbitMQ, retrying in 10s
2024/08/06 07:19:07 [*] Attempting to connect to RabbitMQ at 127.0.0.1:5672, attempt 4/10
2024/08/06 07:19:07 [-] Failed to connect to RabbitMQ, retrying in 10s
2024/08/06 07:19:17 [*] Attempting to connect to RabbitMQ at 127.0.0.1:5672, attempt 5/10
2024/08/06 07:19:17 [+] Successfully connected to RabbitMQ at amqp://mythic_user:***@127.0.0.1:5672/mythic_vhost
2024/08/06 07:19:17 [*] Waiting for Mythic Server and Nginx to come online (Retry Count = 10)
2024/08/06 07:19:17 [*] Attempting to connect to Mythic UI at https://127.0.0.1:7443, attempt 1/10
2024/08/06 07:19:17 [+] Successfully connected to Mythic at https://127.0.0.1:7443
MYTHIC SERVICE WEB ADDRESS BOUND LOCALLY
Nginx (Mythic Web UI) https://127.0.0.1:7443 false
Mythic Backend Server http://127.0.0.1:17443 true
Hasura GraphQL Console http://127.0.0.1:8080 true
Jupyter Console http://127.0.0.1:8888 true
Internal Documentation http://127.0.0.1:8090 true
ADDITIONAL SERVICES ADDRESS BOUND LOCALLY
Postgres Database postgresql://mythic_user:[email protected]:5432/mythic_db true
React Server http://127.0.0.1:3000/new true
RabbitMQ amqp://mythic_user:[email protected]:5672 true
Mythic Main Services
CONTAINER NAME STATE STATUS MOUNT PORTS
mythic_documentation running Up 46 seconds (health: starting) local 8090/tcp -> 127.0.0.1:8090
mythic_graphql running Up 47 seconds (health: starting) N/A 8080/tcp -> 127.0.0.1:8080
mythic_jupyter running Up 46 seconds (healthy) local 8888/tcp -> 127.0.0.1:8888
mythic_nginx running Up 46 seconds (healthy) local 7443/tcp -> :::7443, 7443
mythic_postgres running Up 46 seconds (healthy) local 5432/tcp -> 127.0.0.1:5432
mythic_rabbitmq running Up 46 seconds (health: starting) local 5672/tcp -> 127.0.0.1:5672
mythic_react running Up 46 seconds (healthy) local 3000/tcp -> 127.0.0.1:3000
mythic_server running Up 45 seconds (health: starting) local 7000/tcp -> :::7000, 7001/tcp -> :::7001, 7002/tcp -> :::7002, 7003/tcp -> :::7003, 7004/tcp -> :::7004, 7005/tcp -> :::7005, 7006/tcp -> :::7006, 7007/tcp -> :::7007, 7008/tcp -> :::7008, 7009/tcp -> :::7009, 7010/tcp -> :::7010, 17443/tcp -> 127.0.0.1:17443, 17444/tcp -> 127.0.0.1:17444, 7000, 7001, 7002, 7003, 7004, 7005, 7006, 7007, 7008, 7009, 7010
Installed Services
CONTAINER NAME STATE STATUS MOUNT
apfell running Up 47 seconds apfell_volume
apollo running Up 41 seconds local
athena running Up 47 seconds athena_volume
http running Up 47 seconds http_volume
merlin running Up 41 seconds local
nimsyscallpacker_wrapper running Up 41 seconds local
poseidon running Up 47 seconds poseidon_volume
venus running Up 41 seconds local
websocket running Up 47 seconds websocket_volume
2024/08/06 07:19:17
[*] RabbitMQ is currently listening on localhost. If you have a remote Service, they will be unable to connect (i.e. one running on another server)
2024/08/06 07:19:17
Use 'sudo ./mythic-cli config set rabbitmq_bind_localhost_only false' and restart mythic ('sudo ./mythic-cli restart') to change this
2024/08/06 07:19:17
[*] MythicServer is currently listening on localhost. If you have a remote Service, they will be unable to connect (i.e. one running on another server)
2024/08/06 07:19:17
Use 'sudo ./mythic-cli config set mythic_server_bind_localhost_only false' and restart mythic ('sudo ./mythic-cli restart') to change this
2024/08/06 07:19:17 [*] If you are using a remote PayloadType or C2Profile, they will need certain environment variables to properly connect to Mythic.
2024/08/06 07:19:17 Use 'sudo ./mythic-cli config service' for configs for these services.
Logs from poseidon
ubuntu@ip-10-0-9-160:~/Mythic$ sudo ./mythic-cli status
MYTHIC SERVICE WEB ADDRESS BOUND LOCALLY
Nginx (Mythic Web UI) https://127.0.0.1:7443 false
Mythic Backend Server http://127.0.0.1:17443 true
Hasura GraphQL Console http://127.0.0.1:8080 true
Jupyter Console http://127.0.0.1:8888 true
Internal Documentation http://127.0.0.1:8090 true
ADDITIONAL SERVICES ADDRESS BOUND LOCALLY
Postgres Database postgresql://mythic_user:[email protected]:5432/mythic_db true
React Server http://127.0.0.1:3000/new true
RabbitMQ amqp://mythic_user:[email protected]:5672 true
Mythic Main Services
CONTAINER NAME STATE STATUS MOUNT PORTS
mythic_documentation running Up 7 minutes (healthy) local 8090/tcp -> 127.0.0.1:8090
mythic_graphql running Up 25 minutes (healthy) N/A 8080/tcp -> 127.0.0.1:8080
mythic_jupyter running Up 25 minutes (healthy) local 8888/tcp -> 127.0.0.1:8888
mythic_nginx running Up 25 minutes (healthy) local 7443/tcp -> :::7443, 7443
mythic_postgres running Up 25 minutes (healthy) local 5432/tcp -> 127.0.0.1:5432
mythic_rabbitmq running Up 25 minutes (healthy) local 5672/tcp -> 127.0.0.1:5672
mythic_react running Up 25 minutes (healthy) local 3000/tcp -> 127.0.0.1:3000
mythic_server running Up 25 minutes (healthy) local 7000/tcp -> :::7000, 7001/tcp -> :::7001, 7002/tcp -> :::7002, 7003/tcp -> :::7003, 7004/tcp -> :::7004, 7005/tcp -> :::7005, 7006/tcp -> :::7006, 7007/tcp -> :::7007, 7008/tcp -> :::7008, 7009/tcp -> :::7009, 7010/tcp -> :::7010, 17443/tcp -> 127.0.0.1:17443, 17444/tcp -> 127.0.0.1:17444, 7000, 7001, 7002, 7003, 7004, 7005, 7006, 7007, 7008, 7009, 7010
Installed Services
CONTAINER NAME STATE STATUS MOUNT
apfell running Up 24 minutes apfell_volume
apollo running Up 25 minutes local
athena running Up 24 minutes athena_volume
http running Up 25 minutes http_volume
merlin running Up 25 minutes local
nimsyscallpacker_wrapper running Up 25 minutes local
poseidon running Up 7 minutes poseidon_volume
venus running Up 25 minutes local
websocket running Up 25 minutes websocket_volume
2024/08/06 07:53:20
[*] RabbitMQ is currently listening on localhost. If you have a remote Service, they will be unable to connect (i.e. one running on another server)
2024/08/06 07:53:20
Use 'sudo ./mythic-cli config set rabbitmq_bind_localhost_only false' and restart mythic ('sudo ./mythic-cli restart') to change this
2024/08/06 07:53:20
[*] MythicServer is currently listening on localhost. If you have a remote Service, they will be unable to connect (i.e. one running on another server)
2024/08/06 07:53:20
Use 'sudo ./mythic-cli config set mythic_server_bind_localhost_only false' and restart mythic ('sudo ./mythic-cli restart') to change this
2024/08/06 07:53:20 [*] If you are using a remote PayloadType or C2Profile, they will need certain environment variables to properly connect to Mythic.
2024/08/06 07:53:20 Use 'sudo ./mythic-cli config service' for configs for these services.
ubuntu@ip-10-0-9-160:~/Mythic$ sudo ./mythic-cli logs poseidon
cp /main .
./main
{"level":"error","time":"2024-08-06T07:46:08Z","message":"Error: Version, v1.3.0, isn't supported. The max supported version is v1.3. \nThis likely means your PyPi or Golang library is out of date and should be updated."}
{"level":"error","time":"2024-08-06T07:46:13Z","message":"Error: Version, v1.3.0, isn't supported. The max supported version is v1.3. \nThis likely means your PyPi or Golang library is out of date and should be updated."}
.......snip........
{"level":"error","time":"2024-08-06T07:46:18Z","message":"Error: Version, v1.3.0, isn't supported. The max supported version is v1.3. \nThis likely means your PyPi or Golang library is out of date and should be updated."}
{"level":"error","time":"2024-08-06T07:46:23Z","message":"Error: Version, v1.3.0, isn't supported. The max supported version is v1.3. \nThis likely means your PyPi or Golang library is out of date and should be updated."}
I believe the issue is here:
ubuntu@ip-10-0-9-160:~/Mythic$ git checkout -b Mythic3.3 Switched to a new branch 'Mythic3.3'
I think what you did was update your branch (git pull), then create a new local branch called Mythic3.3 (based on your current, Master branch), then you built the mythic-cli (from master). When you used mythic-cli to install the Mythic3.3 version of Poseidon though, that worked correctly, so you have Mythic3.2 and Poseidon for Mythic3.3 (hence the issue).
I think it might be as simple as like git checkout -b Mythic3.3 origin/Mythic3.3 which says to switch to a local branch called Mythic3.3 which pulls changes from the origin/remote Mythic3.3 branch.
I believe the issue is here:
ubuntu@ip-10-0-9-160:~/Mythic$ git checkout -b Mythic3.3 Switched to a new branch 'Mythic3.3'
I think what you did was update your branch (git pull), then create a new local branch called
Mythic3.3(based on your current, Master branch), then you built the mythic-cli (from master). When you usedmythic-clito install the Mythic3.3 version of Poseidon though, that worked correctly, so you have Mythic3.2 and Poseidon for Mythic3.3 (hence the issue).I think it might be as simple as like
git checkout -b Mythic3.3 origin/Mythic3.3which says to switch to a local branch called Mythic3.3 which pulls changes from the origin/remote Mythic3.3 branch.
ok done thanks for that.
now back to the original issue -> i don't see any auto-scroll in console view
typing a command (in this example getuser) will NOT scroll down and show the output when received, so it's the same as before.
This is how i expected it to be:
Gotcha, I'll look into why the auto scroll seems to be working for the normal view but not the console view. You mentioned another issue originally about sometimes things like ls would show JSON until you clicked away and clicked back. Does that still happen for you?
The ls seems to be fine now, it was rendered right away!
The only thing i notice is the width of the columns that they lake to contains / wrap the button text (this is just ui stuff)
i tried also ps to see if it render right away, and it does- the output looks OK
but on the terminal i got this - should it bother me?
awesome! I'm glad that part is fixed! I think in the browserscripts there's definitely room to adjust the desired widths for certain columns to make sure they are wide enough to show all the data. That's an easy thing we can adjust per script (Mythic isn't defining it, each script is saying like "give me a table with these columns and here's each column's widths")
ok, try pulling the latest from the Mythic3.3 branch https://github.com/its-a-feature/Mythic/actions/runs/10270124358 and seeing if that works for you now with the scroll. It should scroll to the output if you're at the bottom of the scroll window, but if you're scrolled up, then it shouldn't auto scroll down on you
ok, try pulling the latest from the Mythic3.3 branch https://github.com/its-a-feature/Mythic/actions/runs/10270124358 and seeing if that works for you now with the scroll. It should scroll to the output if you're at the bottom of the scroll window, but if you're scrolled up, then it shouldn't auto scroll down on you
I've probably missed your last reply. I have a few days off from work but be sure I'll test it out! Will update here asap, thanks!
It seems to work fine :) Thanks @its-a-feature
regarding the errors while running ps command in poseidon, should it bother me? do I need to do something about it?
2024-08-27 02:24:15.607 pos[2753:32509] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 3. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
2024-08-27 02:24:15.621 pos[2753:32509] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 3. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
2024-08-27 02:24:15.634 pos[2753:32509] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 3. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
Nah, you don't need to worry about them. The poseidon agent when doing ps used to try to do some parsing for the backing plist files for the processes, but macOS keeps changing things and has its own invalid data, so the parsing would throw errors. That's all been adjusted in the latest poseidon code
I think we have all of these addressed now, so I'm going to close this issue. If you have other issues please continue to open up issues so I can get them resolved :)