Historically, PowerShell has been uniformly case-insensitive, with few exceptions. Note: Due to the similarities of many underlying subsystems, PowerShell on Linux and macOS tend to share the same level of maturity in both features and bugs.Įxcept as noted below, the issues in this section will apply to both operating systems.

In other cases (as with the default aliases for ls, cp, etc.), we are looking for feedback from the community regarding the choices we make. In some cases, these issues are simply bugs that haven't been fixed yet. # Known Issues for PowerShell on Non-Windows PlatformsĪlpha releases of PowerShell on Linux and macOS are mostly functional but do have some significant limitations and usability issues.īeta releases of PowerShell on Linux and macOS are more functional and stable than alpha releases, but still may be lacking some set of features, and can contain bugs. Mentioned here but no updates: PowerShell/PowerShell/blob/b25b8df7cae323c376fe4770882ebbfd805fdbf4/docs/KNOWNISSUES.md#command-availability # Known Issues having to install multiple other tools and have to maintain them separately (PowerShell aside). Found tools like chktrust (early 2000’s/not in RHEL repo’s) and osslsigncode (again, nothing in RHEL repo of course) but I strongly prefer to “live off the land” with tools on the OS (or ones in a repo I can maintain) vs. Would love to do this on Linux as well so it would be terrific to have these cmdlets on the Linux side as well. However, all the clients check the scripts signature to ensure it’s valid signed code prior to executing.

I have a centralized script that I host on a tightly controlled server of which thousands of Windows clients pull down and execute to gather system information and send back to Splunk via HEC. TLDR: Any idea on when PowerShell 7.x will have Get-AuthenticodeSignature and Set-AuthenticodeSignature on Linux?

Powershell 7 linux