Problem:
I'm not sure how you work or how others work, but sometimes when I hit my automation scripts I'm not always in the correct folder to save the output. This has caused me the hassle of having to move folders around or if I'm not paying attention, drop test data randomly on my drive.
Proposed Solution:
So what I have done with some scripts I have is utilise the __ED variable I made within the engagement aliases (#12). This script could benefit from using this variable, or selecting the folder, or even passing a directory to store the output.
This would require a refresh to this script and updating how the tools save and to utilise this more dynamic approach to saving.
Example:
--[SNIP]--
############################################################
# Robots
############################################################
echo -e "${green} [+] Curling... robots.txt ${reset}"
curl -s -L ${url}/robots.txt -o ${__ED}/tool-output/robots.txt
--[SNIP]--
Problem:
I'm not sure how you work or how others work, but sometimes when I hit my automation scripts I'm not always in the correct folder to save the output. This has caused me the hassle of having to move folders around or if I'm not paying attention, drop test data randomly on my drive.
Proposed Solution:
So what I have done with some scripts I have is utilise the
__EDvariable I made within the engagement aliases (#12). This script could benefit from using this variable, or selecting the folder, or even passing a directory to store the output.This would require a refresh to this script and updating how the tools save and to utilise this more dynamic approach to saving.
Example:
--[SNIP]-- ############################################################ # Robots ############################################################ echo -e "${green} [+] Curling... robots.txt ${reset}" curl -s -L ${url}/robots.txt -o ${__ED}/tool-output/robots.txt --[SNIP]--