You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am getting an error everytime I try running the default Purplesharp playbook. I have currently configured the range in a local installation The command I am running is as follows:
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: If you are using a module and expect the file to exist on the remote, see the remote_src option
fatal: [localhost]: FAILED! => {"changed": false, "dest": "C:\\Tools\\PurpleSharp\\playbook.pb", "msg": "Could not find or access '././configs/purplesharp_playbook_T1003.pb'\nSearched in:\n\t/home/forensics/attack_range/modules/ansible/roles/purplesharp/files/././configs/purplesharp_playbook_T1003.pb\n\t/home/forensics/attack_range/modules/ansible/roles/purplesharp/././configs/purplesharp_playbook_T1003.pb\n\t/home/forensics/attack_range/modules/ansible/roles/purplesharp/tasks/files/././configs/purplesharp_playbook_T1003.pb\n\t/home/forensics/attack_range/modules/ansible/roles/purplesharp/tasks/././configs/purplesharp_playbook_T1003.pb\n\t/home/forensics/attack_range/modules/ansible/files/././configs/purplesharp_playbook_T1003.pb\n\t/home/forensics/attack_range/modules/ansible/././configs/purplesharp_playbook_T1003.pb on the Ansible Controller.\nIf you are using a module and expect the file to exist on the remote, see the remote_src option", "src": "././configs/purplesharp_playbook_T1003.pb"}
The text was updated successfully, but these errors were encountered:
I am getting an error everytime I try running the default Purplesharp playbook. I have currently configured the range in a local installation The command I am running is as follows:
python attack_range.py simulate -e PurpleSharp -t ar-win-attack-range-key-pair-ar-0 -p configs/purplesharp_playbook_T1003.pb
The error I am getting is as follows:
The text was updated successfully, but these errors were encountered: