omi VS PowerShell

References and further reading https://packages.debian.org/sid/netbase https://github.com/gssapi/gss-ntlmssp https://packages.debian.org/sid/libs/gss-ntlmssp https://www.bloggingforlogging.com/2020/08/21/wacky-wsman-on-linux/ https://github.com/PowerShell/PowerShell/issues/6647 https://github.com/jborean93/omi/issues/29 https://www.crowdstrike.com/cybersecurity-101/ntlm-windows-new-technology-lan-manager/

Did a real quick look around which you've probably seen already, but brew install openssl will probs give you OpenSSL 1.1 and looks like https://github.com/jborean93/omi / https://www.powershellgallery.com/packages/PSWSMan/2.2.0 was updated to tell it to look for 1.1 vs. 1.0 on OSX.

Have you considered a fork of the WSMan lib I've worked on that's distributed through the PSWSMan module. It replaces the builtin WSMan lib(s) to fix a whole bunch of problems that I've mentioned here https://github.com/jborean93/omi#changes-from-upstream-omi. It makes the Linux -> Windows connection through WSMan so much easier to use and fixes one of the fundamental problems the builtin WSMan lib has with HTTPS, no certificate verification.

The WSMan libs provided on Linux for PowerShell are quite troublesome but ultimately I've found that only Kerberos works properly which can be difficult to set up on Linux correctly. I've created a fork for this library which can be found under my omi repository. It fixes a whole bunch of issues with the provided library from PowerShell making it a lot easier to use. To install it you need to run the following as sudo

Then after you close and reopen PowerShell the new library is now used for any WSMan operations. You find find out more about this fork on https://github.com/jborean93/omi.

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.