Conversation

Notices

1. Embed this notice
   kurtseifried (he/him) (kurtseifried@infosec.exchange)'s status on Wednesday, 18-Sep-2024 08:25:45 JST kurtseifried (he/him)

   in reply to

   • Tinker ☀️

   @tinker this is why I keep a file called PROCESS.md where I cut and paste commands and things I run when doing a job like that. For one thing it helps me recall what the heck I did if I need to figure it out the next day, but also lets me see how scriptable or how much work it would be to automate this if I do end up having to do it again and again.

   • Embed this notice
     Jake Hildreth (acorn) :blacker_heart_outline: (horse@infosec.exchange)'s status on Wednesday, 18-Sep-2024 08:25:45 JST Jake Hildreth (acorn) :blacker_heart_outline:

     in reply to

     • Tinker ☀️

     @kurtseifried @tinker I have a function called New-QuickScript in my PowerShell profile. When I run it, my history pops up in a GUI/TUI and allows me to select commands individually then writes those files to a .ps1 file. It even does a quick test to see if the script works as is. It rarely works perfectly on the first try, but it’s nice to have the basics documented.

   • Embed this notice
     Tinker ☀️ (tinker@infosec.exchange)'s status on Wednesday, 18-Sep-2024 08:25:46 JST Tinker ☀️

     That moment during a manual process when you realized you probably should have scripted it... but you've done so much already you're NOW at a point where scripting it would take longer than just finishing it out manually....