Every now and then while delivering one of our PowerShell workshops, my customers ask me “How can I create an exe from my PowerShell script?” And every time the same reasoning is being used: To obfuscate the use of clear text passwords, connection strings and other sensitive data from prying eyes. Sure, most will tell me “The user should not see the script running” but this never seems to be the real reason 🙂
While I hopefully won’t have to tell you, my esteemed readers, the importance of not storing sensitive data in scripts at all, I still wanted to share my PowerShell wrapper (GitHub repo). After all, there might be reasons to use this like creating a transport vessel for your script and it’s dependencies that even executes itself without having to be extracted before.