ShellOpsLog is a versatile tool designed to capture and log all executed commands during various operations, such as red and purple team engagements.
It provides a lightweight solution for tracking command history without recording their output. The logged commands are saved in a CSV file, making it easy to analyze and include in client deliverables or internal reviews.
ShellOpsLog offers two primary implementations:
PROMPT_COMMAND in Bash or preexec in Zsh to log commands in Unix-based shells.source /path/to/ShellOpsLog.sh to your shell startup file (e.g., ~/.bashrc or ~/.zshrc).start_operation_log ~/Projects/MyClient.stop_operation_log.New-Item -ItemType File -Path $PROFILE -Force.Start-OperationLog "C:\Projects\MyClient".Stop-OperationLog.While CMD support is available, it currently has limitations and is slated for updates in the future.
ShellOpsLog provides a simple yet effective way to track command history across different shell environments, making it a valuable tool for maintaining a clear record of activities during various operational engagements.
When I first started learning malware analysis and reverse engineering, I thought the hardest part…
Both git fetch and git pull talk to a remote repository, but they do very different things to your…
Sometimes the change you need already exists, just on the wrong branch. A hotfix lands…
Email is still one of the most important communication channels inside modern applications. Password resets,…
Nginx is a high-performance web server and reverse proxy trusted by some of the largest…
ufw (Uncomplicated Firewall) sits on top of iptables (or nftables on newer systems) and replaces…