PS2EXE VS PowerShell

If you have powershell scripts for your Users you can also try ps2exe. https://github.com/MScholtes/PS2EXE

PS2EXE -- This is what I've used in the past to create a exe from a PS script. Would suggest reading the readme on Github to understand the possible behavior changes while using it.

Something like using this: https://github.com/MScholtes/PS2EXE Although I'm sure there are other utilities out there that do something similar. It's not 100% absolutely secure, because I'm pretty sure that .exe can be de-compiled and read, but at least the password wouldn't be in a .log file (if passed as a parameter), nor clearly in a downloaded {random guid}.ps1 in the CM folder.

PS2EXE

To run with PowerShell save this to a text file with a .ps1 extension. Then right click and run with PowerShell. Orrrr...how I did it is I converted the .ps1 to .exe using ps2exe here https://github.com/MScholtes/PS2EXE/blob/master/README.md. Then just run the exe and just a black terminal screen shows up blank and script runs in the background. To stop the script just close out the black terminal screen. The exe way is better if someone monitors your screen from time to time because it doesn't show what's really going on.

As for how: Been using ps2exe for small app for a client. It's ok, but that's when you already got a script and wanna pack it into exe: https://github.com/MScholtes/PS2EXE

Right from the README.MD...

Yes and no. Maybe this theoretical miner would stop mining to drop GPU usage but who knows what else it's doing or data it's exfiltrating. I at one point (for fun) wrote a key-logger entirely in PowerShell and was wrapped as an executable and ran under the name "Windows Software Update" or something like that... it was a long time ago. The process itself would still be there but malware can be pretty good about disguising itself as other things. Keep in mind what I said about looking for the taskmgr process is probably the most basic way to do this. If someone is writing a legitimate sophisticated malware they're probably not writing it in as a simple .NET FX console app and you're better off just nuking your system and starting fresh.

msiexec.exe /package https://github.com/PowerShell/PowerShell/releases/download/v7.2.6/PowerShell-7.2.6-win-x64.msi /quiet ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=1 ADD_FILE_CONTEXT_MENU_RUNPOWERSHELL=1 ENABLE_PSREMOTING=1 REGISTER_MANIFEST=1 USE_MU=1 ENABLE_MU=1 ADD_PATH=1

This smells like when PowerShell aliased curl and wget to a completely different command, with incompatible arguments.

https://github.com/PowerShell/PowerShell/pull/1901

PowerShell is available on macOS and Linux as well (source on Github: https://github.com/PowerShell/PowerShell). It may not be as well-integrated with things like system services management, but the language still works well. You can still use all the command line tools you're used to on Linux, of course.

nushell does look interesting, though the lack of a .deb repository does put it pretty low on my to-do list.

Issue #7940 discusses potential improvements to array slicing.

Note: This can be problematic as it prevents upstream commands from running their end {} block. See here. The new clean {} block introduced in PowerShell v7.3 does not suffer from this issue.

Can you give an example of something that PS can do that is built-in for text processing, instead of a proprietary symbolic query language?

[1] https://github.com/PowerShell/PowerShell

https://github.com/PowerShell/PowerShell/blob/master/LICENSE... is the MIT license. (Microsoft supplies debs directly which may reduce the motivation for Debian to do so.)

Oh, heh, also https://github.com/PowerShell/PowerShell/blob/master/docs/bu... the build script is written in PowerShell, so there's a bootstrapping problem :-) (Debian has solved those before of course, but with community sentiment like the above maybe noone is motivated to bother.)

According to https://github.com/PowerShell/PowerShell/issues/19628, the default behaviour is invoked whenever the completion script returns no output. To attempt to do so, I tried exiting the script via returning an empty string, or using the return keyword to exit the script completely, unfortunately with no avail. Is there a technique to achieve what I want, and is there any documentation about it other than the official one? Thank you in advance.