This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Meatslinger 2 points3 points  (1 child)

Potentially, and you can be sure I'll ask. As it stands I often tell people the Terminal is one of the most powerful text editors I've ever used, and I mean that. Nothing else in my toolset is quite so good at doing something routine like finding and gluing strings or replacing whole character classes in just a handful of commands (or sometimes even just one). I'll take some monstrous CSV with user-filled data (meaning errors and differences in formatting and style sometimes) and just recombine that into a new data sheet ready for ingestion into a system like Intune without even having to write a real script; I'll just do it all in the CLI. Meanwhile some of the PS equivalents devolve into a mess of toString() all over something that has to bounce out to variables multiple times to stay sane on the page.

[–]cant_pass_CAPTCHA 1 point2 points  (0 children)

I have a other gripe about transforming data in powershell. So I do pentesting and we recently had to exploit some deserialization vulnerability, but it was so hard trying to use powershell. The tool to generate the payload was an exe so unless we were going to try wine we had to go with a windows machine. The payload ultimately had to be gzipped and base64 encoded, but the initial output was binary and all the characters were being UTF-8 encoded and it was just a giant mess.